I am about to release the 2nd version of my app, however, I seem to face console logs that seem a bit frustrating. My app works completely fine even with the issues, but these console logs are delaying my App Store submission. Will Apple take into review the console logs or not? Thanks for any help
The console log is not matter in your app review from apple. You can simply remove the unnecessary logs from console with add environmental variable from edit scheme like below:
I hope it will help you regarding your problem or issue.
Thanks.
Related
I had completed a Flutter app, which seems to work well in simulator. I then went on to release the initial version of the app to AppStore Connect and sent it to beta testers via TestFlight and they were able to test it without any issue and sent me some feedback.
I made a few changes to the app based on the feedback (nothing too drastic) and tested it throughly in the simulator which seems to work fine. But now when the users download the app via TestFlight it crashed while opening and I cant seem to fix it no matter what I try. Any help would be really appreciated
So far I have tried,
Followed this article letter to letter
Modify optimisation parameters in Build Settings as mentioned here
Tried this SO answer
Crash report from XCode is not much of use since it is not very readable (as attached in the picture).
Can't yet seem to find any reliable answer, Any help on this would be much appreciated.
Please guide me! Why Firebase console take much time to communicate with server. I'm waiting one and half hour to complete this takes. Anybody tell me what is the reason behind this issue or anyone facing this issue before.
Not show the Graph.
Please make your app force fully crash 2-3 times, after disconnecting your app from Xcode.
This is what worked for me.
In my case, I solved this problem by doing these steps:
Make sure you follows the all steps that mentioned in Firebase Documentation Crashlytics.
Use fatalError() for crash your app.
Uninstall App from simulator or Real Device
Run the app on Simulator or Real device then stop running.
And then Open the App that Install on Simulator or Real device.
Open Firebase Console project And Refresh it.
This can happen as a result of several different issues, however they're usually connected to your app being unable to make the proper call to the Crashlytics settings endpoint. You can either write in to Firebase support, or feel free to start a private thread with me, and I can check your apps settings in the Firebase backend.
if you followed all steps as per latest crashlytics documents!
try forcing a crash directly with button click on initial view instead of just building and running your app
use fatalError() for crash your app
I have currently downloaded my Crashlogs for the current version of my iOS App. And I have seen a strange message which I cannot understand:
[NSPersistentStoreCoordinator(_NSInternalMethods) _checkRequestForStore:withContext:originalRequest:andOptimisticLocking:]
The exact stack
What do you think about this log? I think it has something to do with saving a current changes in the store.
Could you please help me improving my app.
Try to add the lightweight Migration to your App
or
For temporary solution while development, you can delete your app from simulator or any device and run it again. Hope it will solve.
Reference
So I have two apps successfully submitted for TestFlight Beta Testing (See image below).
For the first one, installation works as expected. For the second one, the app appears "stalled" at around 90%. Never gets passed what's shown in the image. However, if I return to the home screen the app has installed (no install progress indicators on app icon) and appears to be functioning normally.
I receive no errors within TestFlight and no error logs are produced. TestFlight just never shows the "OPEN" icon for this particular app.
Some other External Testers are also seeing this so it leads me to believe it has something to do with my build and it could be something I can fix. (I do not know if all external users are seeing this issue). Biggest concern is this will happen to some users when the app is released in the App Store and they will end up losing their data.
I have tried deleting and re-installing the app with no success. I have also tried killing the TestFlight app process. "Stopping" the install simply shows "INSTALL" and reselecting gets to what's shown below. Version updates also display the same issue.
Anyone have any ideas on what may be wrong with this particular app?
#kanso already posted the solution. So be aware of using bad app version numbers ;-)
The issue was resolved using a build number that does not contain a '0' following a '.'
for example,
Build Version: 1.1.002 # no good
Build Version: 1.1.2 # WORKS
Ive seen this, and it seems a bug in the test flight app, since the applications seem to install properly as you mention.
You don't need to worry, it is a bug by Test Flight. People have registered their complaints. Hopefully, they will fix it soon.
I have a serious issue which I cannot seem to solve.
Recently I have made an update to an IOS app, and when testing in XCODE as both Ad-Hoc, Debug, and installing via the .IPA on a device the issue cannot be replicated. However when I download the app from the App Store, it crashes.
Does anyone know how this could happen, and any potential solutions? I am getting lots of complaints from users, and not sure what to do?
Could part of the binary upload have got corrupted?
Probably you always compiled your app in debug mode. But when sent to App Store you made a release compile. click the arrow in the run button select scheme and chose "release mode" and run your app it will probably crash.
check if you used NSParameterAssert as they are not called in release mode
I cannot say why your live App Store application is crashing and the debug version is not. Two possible solutions:
Crash reports:
To find out why your application crashed, you might want to check if there are any crash reports available on iTunes Connect. Log in on iTunes Connect and click on your application. Scroll down to Crash Reports. You will find out more about why your application is crashing here.
More information about crash reports here at Apple's own iOS Developer Library.
Prerelease your app with TestFlight: For in the future: test your application by uploading it on iTunes Connect and testing it with TestFlight first before submitting the application to the iTunes Store. This will save you a lot of (review) time if you find a error.
I realize this is an old thread but I had the same issue with my App that I released. Meaning it worked fine in testing, but when I released it it would crash. The culprit ended up being the fact that I am using In App Purchases. I have two items that can be "bought" but I had only enabled one of them. In testing it was able to read both of them, but with the release version, it was only pulling the one that was enabled down, creating the crash. The fix was simply enabling the disabled item. I didn't even have to redistribute the app, though I had to wait for it to "percolate" through... Anyway this may help someone in the future.
Check if your app is looking for too many IAPs.
I just had this problem and my problem was I had deleted an IAP from the App Store, but didn't remove it from the app code.
For some reason it only crashed when downloaded; I used a promo code to do this before launching my app.
Thanks to Tornado for the inspiration to try this variation.