After users upgrade their devices to iOS 13 our Xamarin iOS app opens and immediately crashes, but if the users then completely uninstall and then install the app it works perfectly fine.
We use AppCenter to track our errors but the app is crashing before it event gets to the setup of the connection to their service meaning we have no errors logs to help track the issue.
Is anyone else experiencing a similar issue or have any more info to help us track down the problem?
Related
I have noticed on iOS 15, when I install an app from TestFlight, my app icon is not appearing on the device. Only placeholder for app icon appears on physical device.
All app icon assets for every resolution are correctly added to Assets. The app icon appears in the test flight app and in appstoreconnect everywhere including TestFlight and builds.
The only place it doesn't appear is on the device. It appears normally on the simulator.
The only fix I found was to add a version of the app to add a build where you submit for review and save it. No need to submit. Then install from TestFlight and reboot device. The problem is as soon as I uploaded a new build to TestFlight it stopped showing icon and had to go through this silly process again.
I have never had this issue with past apps and wondering what the issue is and how to resolve it.
I encountered the same issue with testflight on iOS 15. I found this from apple developer forum that might of help:
https://developer.apple.com/forums/thread/682648
According to the accepted answer by #vladweinstein, a temporary solution is to restart the device after installing the app.
This works for me too.
We are still having the same issue with TestFlight apps (iOS 14.7 and iOS 15+)
The only solution we found is to restart the device as Raphael Rex mentioned.
I have a Xamarin.Forms Android app on the Google Play store. An overwhelming amount of users are leaving 1 star app reviews of my app saying that the app is "Freezing." They say that nothing happens when they click on a button in the apps UI. I have made doubly sure that no processes are running on the UI Thread that might hold up the UI. I have not been able to recreate this "Freezing" behavior personally. There are also no crash or ANR reports in the Google Play Console (at least not enough to make up for the amount of negative reviews I'm receiving). Has anyone else faced this problem?
Useful Info:
Xamarin.Forms Version: 4.8.0.1560
There is no discrimination between the Freezing behavior and users' Android API Version
The issue is not happening (or is not being reported) on the iOS app.
Do you have a physical Android device to deploy to? Take the apk and side load it, or download from the store, don't use VS to deploy the app on your device.
I had a similar issue and it was the code shrinker in VS. The released version with the code shrinker enabled, caused the app to freeze immediately after the splash screen.
You can disable it by selecting 'nothing' in the code shrinker box in VS.
I have a problem during the configuration about the crashlytics integration.
I configured correctly the sdk into the app.
I insert firebase.crashlytics().crash(); for simulate the crash, but I receive this issue (below the image) and I don't see the crash in the firebase dashboard.
How can I solve the issue?
Thanks
Disconnect your xcode from your simulator / device before crashing the app. In this case the xcode debugger intercepts the crash and the report is not sent over to crashlytics
I'm wondering if there's a known bug in WatchOS 6.1.1 regarding local notifications triggered from the watch?
I have an app that I developed about two years ago on watchOS 4. It would send local notifications from the watch during background processing. It worked great. The code sat for about two years and I was asked to update it. Since updating, I cannot get local notifications from my watch to work when I distribute builds through TestFlight. When I run the app through Xcode it works (both with the Debug and Release schemes). I saved logs in the watch app that show that the UNUserNotifications.current.add() does not pass an error into its completion handler. I can get local notifications from the handset in TestFlight builds to work and I can mirror those on the watch. But I cannot get local watch notifications to work. Does anyone have any idea why this might be? Is there a known bug? Have local watch notifications changed in a breaking way since watchOS 4?
I've found my issue. I think it's a new bug in watchOS6. It seems that permissions aren't being properly communicated from the handset to the watch. After giving permission for notifications on the handset, I would check for notification permissions on the watch and get .notDetermined. Strangely, if I downloaded the handset app and quickly gave notification permissions BEFORE the watch app had finished downloading, then it properly received notification permissions. I fixed this by simply requesting notification permissions on both the handset and the watch.
I'm rewriting my watch app to work in watchos2 but have problems debugging on the actual watch (XCode7). What is the correct way how to do this?
1) Obvious (but naive) approach - connect your phone with paired watch, in XCode select Extension scheme to run on Phone + Watch. Click play and it should work, right? This seems to work only just after fresh pairing and breaks very quickly (after few debug runs). See issues and behaviour below
2) Run phone app first then add run of extension - this approach worked for me longer but eventually broke as well.
3) Unpair and pair again - more than painful experience, time consuming and not practical at all. Will help for a while though.
Main problems:
phone app not communicating - I've seen not reachable or messages just time out
watch app stops running - XCode is saying it's running but it's not - won't even attach. If I run it manually on watch most of the times it will attach but then the phone app is not reachable
watch app won't even install - I suspect when the XCode is saying it's running it in fact it doesn't because when I remove the app from watch and then run XCode goes through the whole install process and "running" but the icon doesn't even appear on the main screen
phone stops reacting when I use option 2) and try to run something else while app is attached
phone seems to be blocked, selecting other apps (even going back to my app) won't work until I kill the session
Setup: The phone and watch is paired correctly, phone can see watch, watch can see phone, other apps are working. Watch "trusts" the computer as well, app is "shown on apple watch". Phone is 5s 9.0.1.
I've tried various restart combinations (phone|watch|xcode|mac), shuffled cables, disconnect, reconnect, etc. but that didn't help either.
Did anybody find a usable way how to debug watchos2 app from XCode? Nobody else seems to be complaining about this with released XCode7 though I've seen lots of similar issues in beta builds.
Use Apple watch recharging cable, connect your watch to developing Mac that runs Xcode.
It provides much more successful and fast debugging.
I have been dealing with the same issue this last days, I just updated to iOS 9.2, watchOS 2.1 and XCode 7.2, and now everything works.
After update XCode to 7.2, iOS9.2 my phone and WatchOS2.1 my Apple Watch the debug process is better. I suggest to update all your devices.