I worked on some bugs for an app and the fixes seemed to work fine on the simulators and physical devices I tested them on. Now that the update has gone live though, I have reports from users saying the same bugs still exist. I downloaded the app from the app store instead of loading it from xcode and indeed the bugs are still there. Has anyone one else ran into this issue? If so do you have any idea if it is a problem with xcode, ios, the app store, or something else?
EDIT:
I've done some more looking around about '.ipa'. Is it possible that the live '.ipa' is different from the one that was submitted?
Related
I'm facing a strange issue with universal links on iPhone - iOS 12.2.
I'm trying to open the APP using a registered universal link (the same link works on other devices using both - the same and different version of iOS), using identical application (the same version).
What's strange is that I can't even find the option to open the link in a native app when holding the link for a while on this device, although I found it in other devices.
It used to work, but then suddenly stopped to open the APP. I tried rebooting and reinstalling the app.
Did anyone face similar issue? Any suggestion in debugging? I'd really like to avoid factory reset of the phone.
You might be running into either of these two bugs:
https://openradar.appspot.com/45201697
https://openradar.appspot.com/33893852
I just ran into this. Deleting the app, reboot the device, wait an hour or so (unsure of time needed to wait) then reinstall the app. That seems to force it to re-check the AASA.
Seems like there could be a process running after reboot blocking swcd from running.
Have you tried to delete the app and restart the phone to check if this is not a apple-app-site-association problem?
So after upgrading to the newest iOS the problem still remained in Chrome.
I was able to open the contextual menu and open the app through the Open in... item from Safari, and since then it works as expected across all the browsers. This doesn't explain the origin of this issue, but I hope this will help you as well.
I am somewhat new to developing apps for iOS and I have been creating a few demo projects in Xcode. My problem is the following:
I have been following a few tutorials from Udemy.com and I created an app using firebase, the app works fine for about 3-4 days of use. But after more time passes by, the application does not launch on my device or the simulator. I thought I must have done something wrong when I did the tutorials, so I did them again but the same thing happens after 3-4 days of installing the app. They immediately close after I try to launch them. However, they do work if I rebuild the app on my phone or on the simulator. I do not seem to understand why this happens. has anyone else come across this problem? Or is this a normal thing that happens until you upload the app via the app store? Thank you guys, hope someone here knows. Cheers!
in such case you can check your GoogleService-Info.plist file or get idea about what's wrong by check the App terminate reason printed in your output Console.
I'm here because I'm totally jammed on a problem, and I need some suggestions of where to look for an issue. I submitted an update to my iOS app, and when users try to update the app, the app no longer goes any further than the splash screen. They have to uninstall and reinstall the app for it to work properly.
I've testing the upgrade locally through xcode, and I tested it using TestFlight, and can't reproduce the behavior in either case. Does anyone have an idea what this could be?
Edit
I should also add, there is no crash. It just hangs there.
Did you use Local database in app, previously?
if yes then migration is required, if you make changes in Database.
i think it maybe issue.
After upgrading some of my devices to iOS 10, I am unable to download ODR contents anymore within my app. Devices which still have iOS 9 are still working without a problem.
Does anyone currently suffering from this problem? Any suggestions on how to fix this?
I logged an Apple Developer Technical Support Issue (DTI) on this as I could not find anything that could fix the issue. After a lot of back and forth I got this from them:
In iOS 9, the ODR was handled by the OnDemandD daemon inside the OS. However in iOS 10, we switched ODR to now be handled under the AppStoreD daemon. There were some issues that arose from this transistion, including this specific issue. Also, this issue was on our side of the table, so it’s nothing you or your users did.
I cannot get into the details of the issue, because I honestly don’t know what they changed, but as far as I know, it is stemmed from the daemon transistion above.
Now that iOS 10.2 is out, and will be updating across the iOS fleet, hopefully we'll see and end to this issue. In the meantime my game has been getting bad reviews and feedback from players experiencing a black screen instead of our game levels. :-(
I had the same problem after updating some devices to iOS 10.
I solved it by setting the loadingPriority of the NSBundleResourceRequest to 1.
A user has reported that my app suddenly won't launch on their device. They sent me a video, and they launch the app, the launch image screen shows for a split second, but then crashes back to the iOS home screen.
The user tried deleting and reinstalling the app with no benefit.
I use Crashlytics, and am not getting any reports of crashes from them (or any other user- although I've seen them in prior versions so I know it's working correctly). I'm also not seeing any crashes in iTunes connect.
I asked the user to send me any crash reports in the Settings Diagnostics section and they said there are none listed for my app.
I have confirmed that their iOS version is supported by my app. (iOS 8.4).
I'm not sure where to go next, and would appreciate any pointers. Sorry for the vague question but I have posted everything that I know about the situation.
Just wanted to provide some closure on this. The user ended up wiping and restoring their device, and it solved the problem. It seems extreme to me but it was their own suggestion and didn't take them long to do. So I'm not sure what caused this but that's one (albeit brute force) way to fix it.