recently I've rewritten native iOS and Android apps (Swift, Java) to React Native. On testing, everything works fine, but when the application has been published to Appstore and Play Store, many (if not all, only judging by the users that contacted me before rollbacking to previous version) users were on update greeted with black screen. Once removing the app and installing it again, everything worked fine.
I can't really pinpoint any reason why this would happen. Has anyone met with this problem before?
Thanks
I think it is related to stored user data (user preferences).
It seems that you are depending/using the same old users' preferences keys/values which is tricky to pull off.
Related
I have developed an Android app using react native.
When I run on simulator its fine, and also when I debug via USB on real device its fine.
However when I publish to Google Play store and download the app as a regular customer it sometimes crashes.
Are there any logs somewhere that I can refer to in order to identify what the issue is? Or perhaps there is something I can add to code to help identify where/why issue is occuring.
You can use log errors to do so, record the activity of user. When the app crashes, your app can ask the user to send the bug report.
Using that bug report you can understand why your app crashes.
You could also use tools like Sentry or Firebase Crashlytics with an Error Boundary
wrapping your app to report errors, allowing you to have a better understanding of the production errors by displaying the full error stack trace and a lot more.
I recently created an application with ionic capacitor, in it I use login with google, but I have the following drawback, on some phones (very few) it does not log, it stays on the consent screen, and when they press allow, it shows a loading and returns to leave the consent screen, over and over again, as in an infinite cycle, the thing is that I cannot replicate this on any device or emulator, it has happened on android 8 and 5.1, I even downloaded an emulator with android 5.1 and still I am not able to replicate the error, 90% of the users do manage to enter.
I do not know much about android, however I was reviewing the official documentation and it is identical to the implementation of the plugin (except for the calls to javascript after finishing), I thought it could be the configuration in the console, but I do not think, since as I said in 90% of the devices it works fine.
I would really appreciate if anyone could give me at least an idea on how to replicate the error, or something like that.
this is the plugin in question, in case it is of any use
https://github.com/CodetrixStudio/CapacitorGoogleAuth
I do not share code because I am sure that the problem is not in javascript
these are the scopes i'm using "profile", "email"
I'm trying to reach TestFlight on iTunesConnect but it keeps only the loading spinner and do not show anything. I've tried with Chrome and Safari without success.
http://prntscr.com/8sv799
In my other application on the very same account everything works correctly.
I've already written to support waiting for their response.
My issue was resolved from the support team. They didn't provide me full details what caused this, however after sending them needed information(including page source code) they fixed it on next day.
So if you experience the same, I advise you to contact them(via iTunesConnect).
I've created a Mac App for Mavericks that uses MapKit. It works fine during development and testing on Xcode 5.1. Now I'd like to submit it to the App Store and I need a Distribution Profile which I've created successfully. Trouble is, as soon as I add it to my project, the app doesn't run anymore - it crashes every time without fail with this error message:
When I change back to "no provisioning profile", or to the profile that Xcode created during development, the app runs again.
My question: Is this expected behaviour, or will the app be rejected by the review team? I know that iOS apps don't run with their distribution profiles, but I'm new to Mac Development. Any insights into this way too complex topic are appreciated!
My app was approved - and the crash was indeed no issue for the app review team.
I had a chat with Apple about this who were kind enough to call me back and explain the issue. Looks like this phenomenon is "kind of" expected behaviour: Mac Apps may or may not crash when run with a Distribution Profile.
To avoid this problem, we can add both a Development AND a Distribution Profile to our app, without one having to replace the other. This was news to me. Had I however opened my tired eyes a bit wider I would have perhaps spotted the little disclosure triangle myself:
Perhaps this helps those with the same issue.
I have an app that relies on CoreLocation. In the last week I've had two users send me an email letting me know that location doesn't work anymore in the app. It's a fairly straightforward app that has the ability to display weather based on your current location.
The users swear that location services is enabled, even for the app specifically. In both cases, everything worked perfectly when they first purchased the app but stopped working all of a sudden (their words).
I've had them do several things for me like use other apps that use location services to see if they work or try from alternate locations. They've even uninstalled my app and re-installed to no avail.
Am I crazy or is the users? It just sounds farfetched to me, but I'm far from an expert at this. In both cases they're using an iPod Touch and/or iPad wifi only model. Both are running 5.0.x.
A re-install of the app should certainly reset things to default, right? Do remnants of an app linger around only to be used on a re-install?
In looking through my code I realized that I changed from StartUpdatingLocation to StartMonitoringSignificantLocationChanges which only works on the iPhone 3GS and up. Since it doesn't work on the iPad/iPod Touch this was creating my issue. I changed my code to start the app using StartUpdatingLocation and once a location is received switch over to StartMonitoringSignficantLocationChanges. This resolved the issue for all iOS devices.