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.
Related
In my iPhone 7 iOS 11.1.2, a black screen with spinning wheel appearing for few seconds and asking passcode. It happening frequently in same interval. This same issue is getting in iPad too.
Is this a problem of iOS 11 ? Anybody facing the same issue ?
all
Updating to iOS 11.2 fixed the issue in my case.
I tried and failed updating via iTunes, where I got error messages.
I took the time to do my backup then I went ahead and downloaded via the phone itself the update.
This was a bit hard however since when the screen is up, the phone hangs up every so often (quite often in my case).
I then just proceeded in letting the update complete itself before attempting to open the phone. (It takes a while.)
It seems the issue was/is linked to a crash on push notifications.
In my case, shutting down all of the notifications wasn't a practical option (as seen on other boards) since I have a massive amount of apps I would have had to untoggle to not receive their notifications.
Best of luck on updating to iOS 11.2.
Yes this is an issue that most of the users face recently which re-springs the device in 30 seconds interval from 12:00 AM PST. Some problematic apps that push out notifications in regular interval causes this issue. Like OP said, disabling notifications will help solve this. But it is HIGHLY RECOMMENDED to update your OS to the most recent version or at least to 11.2 to completely fix this issue.
For more info. about this problem, check out this video and this video from Everything Apple Pro.
Note: Your question is not a technical or question related to programming. You should have posted this to the respective community.
I got this issue when setting local notifications using userNotification framework. After a lot of research I found the key problem for the issue that I was setting notifications for the date which is lesser than the current date. I set the notifications only for the future dates then the issue got solved. And this issue occurring only in iOS 11.1 .
Hope this helps someone.
6S, iOS 11.2, Do Not Disturb does not help. Airplane mode doesn't help too (how the notifications can come in Airplane mode?!).
Installed 11.2.1 update and it helped.
But here's how my notifications look like now - https://imgur.com/a/UP88X
I’ve implemented push notifications for our app.
on iOS 9, the sound words fine.
on iOS 10, it’s very unpredictable. Fresh install from Xcode on iOS 10.0.2 would bring up my custom sound. reinstall would bring up default sound. I don’t know exactly when but at times I also get no sound.
reading from here and many others my conclusion is that it works after a hard reboot. 2 questions:
Has Apple completely fixed this issue in any version? If so what version?
After a hard reboot, would the problem completely go away? Or you need to do it again? if so when?
Has Apple completely fixed this issue in any version? If so what
version?
Based on JAL's comment Apple has fixed in iOS 10.2.
After a hard reboot, would the problem completely go away? Or you need
to do it again? if so when?
Based on leontx's comment, For those users who are using iOS 10.0.x or 10.1.x they would only need to do a single hard reset.
There are previous topics about waking up an application from the background with BLE advertisement (e.g. How to wake up iOS app with bluetooth signal (BLE), Android / iOS - BLE - wake up a terminated application when a BLE device connects).
However my question is not about that since we had this feature working fine up to iOS 9.2 included.
Coming iOS 9.3 the feature doesn't work as it used to work before, it seems that the terminated by user swiping off the application is not woken up. Nothing changed on the BLE advertisement originator.
After a recheck of various parameters and reading of Apple documentation, nothing springs to our minds. Neither Apple documentation mention any change, unless we missed something.
Have other people notice this issue? Are you aware of a solution?
We wrote to Apple and we are pending on an answer but maybe somebody here has the correct tip.
Many thanks in advance for the attention.
UPDATE: After more testing, it seems that only when the user swipes the application out the wake up doesn't work like it used to in iOS 9.2
Initial testing were more manual and gave us the impression that there was an underlying issue. However not sure why this change took place without any notification from Apple. - Above text was amended based on the update -
UPDATE 2: This issue is not present anymore in iOS 10.
It turns out after a reply from Apple that this is a (new) intended behaviour.
didEnterRegion/didExitRegion events stopped working from the background after update to 9.3
I have an app that has been working almost perfectly for the last 6 months, and after the update these events are no longer getting called. I started this app over last year when I heard about iOS9 coming out, and when I couldn't get the old one working, I started a new one using Swift instead.
After some time and a LOT of driving in and out of my Region, I got the app to work more reliably than it ever had before. I have several devices using the app, and when all of them updated to iOS9.3/9.3.1, the app stopped calling didEnterRegion/didExitRegion events completely.
I have a ticket open with Apple, but I am getting a lot of push back about the service, and that 9.3 didn't change background location at all.
My devices use AT&T of Verizon, we have tried wi-fi assist on and off, I even wiped a system, formatted the HD, installed El Capitan, and XCode 7.3, and it's hasn't helped.
I also found an issue with the Devices Tool, and when you download the Container, and open package, the Documents folder is empty. I'm not getting a warm fuzzy feeling for Apple right now, and I am sure someone is feeling my MEGA MIND WEDGIE at this moment.
Help....
I have been working with iBeacons for the last few months. I have just recently updated to iOS8 Beta 1 and have found that region monitoring and ranging no longer works on my beacon apps.
It is being caused by permissions. I now get a kCLErrorRegionMonitoringDenied error returned when attempting to start region monitoring. This error corresponds to a user deselecting the location permissions for the app.
If I go into Settings>Privacy>Location Services I get some weird behaviour. Sometimes my app appears on this list with no setting chosen, and other times it doesn't appear on the list at all. If I manually change the setting to 'Allow' and then close Settings, then go back to Settings>Privacy>Location Services I have the same problem - the app might not appear on the list or the settings are not set.
This is obviously a bug in iOS8 beta, just wondering if anyone else has this problem and/or found a workaround?
For iBeacons in iOS8, you must use requestAlwaysAuthorization, not requestWhenInUseAuthorization
(via: http://nevan.net/2014/09/core-location-manager-changes-in-ios-8/)
I don't know what the issue is, but I was having the same problem, I found that going back to Xcode before the beta solved my issue. I wish I could give a better answer than that, but I guess the problem might be somewhere in Xcode and not ios 8.
I actually did more research into this and it seems ios 8 requires some authorization setup before trying to use location services. This might help answer your question further. Here are some links to direct documentation that you might find useful.check out the requestWhenInUseAuthorization documentation on info plist key This should help keep you in Xcode 6 with ios 8. sorry if I wasn't more helpful I'm fairly new to ios development.
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?