I submitted my app update for review a week or so ago and it worked fine for me when i submitted it (on multiple devices and emulator). Apple reviewed it and approved it and now whenever users download it, the app just hangs at the splash screen forever. On iOS 6 beta it immediately crashes. I believe it must be something wrong with the package that Apple put on the store for download, but i honestly have no idea. Anybody had this happen before or anyone have any ideas on how you can debug a problem like this?
This is maybe the 30th or so time i've submitted something to Apple and this is the first time anything like this has ever happened. I have used a technical support incident to contact apple and no response so far from that. I also used the contact us page on the itunesconnect portal to ask about it and no response from that either. Both of those were done on Friday. As a secondary question, does anyone know how long it takes to hear back from Apple when you submit questions in either of those ways?
I faced the same issue. It was a DNS issue. It drove me mad for months, since I could not reproduce the issue. However one poorly configured WiFi helped me reproduce the issue by chance.
iOS tries to perform DNS lookup at the beginning of the app lifecyle. This is even before a single line of code is executed. If the DNS lookup is performed on the main thread synchronously, it blocks the UI. This issue arises only in cases where its trying to resolve the DNS for about 30s while blocking the UI. Hence the iOS watchdog kills the app due to a timeout. Apple also has a doc for this- https://developer.apple.com/library/prerelease/ios/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/CommonPitfalls/CommonPitfalls.html
You can search for DNS lookup in your code and check its execution. In my case it was a 3rd party C-library that was causing an issue.
I know its been really long since this question was asked, hope it helps someone.
Related
We have an app that registers and runs a NetworkExtension (specifically NEPacketTunnelProvider) on both iOS and macOS. This works fine (although not in the iOS simulator, of course, known limitation). However, when the network extension is running, the App Store on macOS/iOS, and TestFlight on iOS, fail to update the app. It looks like they're waiting for the NetworkExtension to terminate, but not actually asking the VPN to disconnect.
We don't want our users to have to think about killing our VPN (which should stay connected whenever possible), but we don't want them to have to think about updates either - they should happen automatically.
Are we missing something? Is there an event we should be listening on to detect that the store is trying to install an app update? Conditions when we should arrange for the VPN to terminate, safe in the knowledge that it will be restarted again after being updated?
Apple had bugs regarding this issue. It was supposed to be ok since iOS 11 (and macOS 10.13 or 10.14), but then users reported that the problem still exists. Several bugs regarding this are still probably open at Apple's bugs reports, but we can't check their status.
You can ask again at their forum, and open another bug regarding this issue.
Probably there's nothing else you can do.
Those are only some of the reports related to this issue:
https://forums.developer.apple.com/message/174708#174708
https://forums.developer.apple.com/thread/92603
https://forums.developer.apple.com/thread/126471
https://forums.developer.apple.com/message/149563#149563
https://forums.developer.apple.com/message/183927#183927
Edit: Someone just posted a question regarding this at Apple's forum. It might be you who posted to question, but maybe it's someone else, so there's another reference:
https://forums.developer.apple.com/thread/128894
So I've been working with FIRAuth to log users into my app with no real problems up until yesterday when I was greeted by this awful message.
Not being terribly familiar with this part of Firebase, I waited for the Token auto-refresh to occur a few times, just to see if my firebase calls would ever come back to me, but sadly they never did.
Above is the method that I'm calling, which I show evidence of in the next picture:
Sadly the second breakpoint is never reached, hence leading me to believe that the Firebase call cannot even return an error because of the the Token issue.
Here's the strangest thing: this bug only occurs on simulator. Running the app on my personal device doesn't result in any issue.
Any help would be greatly appreciated; also don't hesitate to ask for additional information.
Alright well I managed to fix it by switching Simulator devices. Specifically I went from an iPhone 7 Plus to an iPhone 6, but it's curious because I've attempted restarting the simulator before this. Hope this helps anyone who runs into the same problem that I did!
OK, this issue is discussed in this thread, this thread and this thread. However, none of the "answers" seemed to actually address the issue.
This weekend, I submitted my app for beta-test review -twice. It bounced each time. It is now back in review again, and hasn't bounced (fingers crossed).
Each time, was because of an immediate launch crash. Fair enough. I wrote a bad app.
Except I didn't. When I tested in debug, and even release mode on my device and in the simulator, everything worked.
I was finally able to reproduce the issue by archiving and then manually installing the archive through iTunes.
Once I did that, it suddenly started happening when I ran in release mode in the debugger.
Hate it when that happens.
In any case, it was the 'dyld_fatal_error'. In my case, no matter what I did, I couldn't get it to spit out any information at all about what library it was having issues with. The crash reports I got back from Apple were worthless.
What finally solved it for me was basically completely dismantling my app, and putting it back together again. I removed all linked libraries (they are still gone), revoked every one of my certs, and rebuilt the profiles. I de-linked my tests, and re-linked them.
I used to live in Africa. I have a for-real Ju-Ju stick, which I shook at the device for good measure.
Something in there worked (I think, I still have to get a pass from Apple). My money is on the Ju-Ju stick.
The question is: Does anyone know of a DEFINITIVE (not all these WAG responses) reason for this error, and how it can be diagnosed?
I work with a large(ish) app and every update we submit causes us to receive a handful of bad reviews regarding the app download "stuck", "not finishing", "freezing".
This has been happening since iOS 9 but it feels like its becoming increasingly more common.
Our users say the app is frozen, won't open, and can't be deleted or re-downloaded.
Some users have success after restarting the device. But some users swear its become impossible to remove the app.
I've contacted Apple in regards to this but haven't yet got a response.
Has anyone else been experiencing this trend? Is this something I've done incorrectly with my build causing these issues?
Any information is appreciated.
Thank you.
I am quite stumped right now - I released a new update for my puzzle game app few days ago, and I started getting reports that the game shuts down whenever the user tries to enter the store. The store connects to the InAppPurchaseManager, gets the list of all the IAPs, and opens up the store view.
In debugging mode, I had no problems, and it even passed the review without problem! And now the game is freezing on all the users who try to give me some money!!! :S Did anyone else run into this problem? My store was working fine in previous version. Only thing that I changed was I changed the items that could be purchased so I removed some and added some.
Also I noticed that whenever user tries to enter the store WITHOUT internet connection, it works fine. It only freezes when the user has the internet connection (very ironic...)
Any input or past experiences would be very much appreciated!!! Thank you for saving me from this insanity!
Solution - In itunesconnect, in the manage IAP section, I turned off the IAPs that were not being used anymore, but apparently my program was still trying to receive one of the IAPs that was not being used anymore from the IAPmanager, so it was not receiving the product and crashing. I think anyone running into same problem as me would be rare, but if you do, here it is :) happy coding!