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....
Related
We have an app which is monitoring one location. Lately we have noticed that sometimes, ios app doesn't send notification for enter. Things are working fine with android app.
I was reading up on the documentation and the only litmition i found is that an app can only track 20 locations. Which isn't the case in our app. We are tracking only 1 location.
I also looked into if the app has proper implementation and it does, thats why we get notifications sometimes and sometimes we don't.
The other thing that i could think of is if the cell phone was in Low Power Mode. That's one pointer for me so far.
Is there anything else that i could look into to figure out the issue?
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 have a need to update my managed app running on a large amount of iPads without any user interaction. These devices all have the managed app locked in Single App Mode. As I understand it, it's an iOS limitation that an app cannot be updated if either of the following conditions are present:
The app to be updated is in the foreground.
Any app is locked in Single App mode.
With our use case, both of these conditions are present. I also understand that the current workaround is to do the following:
Disable Single App Mode.
Enable Single App Mode for a different app (e.g. Safari) to bring that app into the foreground.
Disable Single App Mode.
Update app.
Re-enable Single App Mode for your app when the update finishes to bring it back into the foreground.
While this method works, it has a lot of drawbacks:
It's highly manual, we have not found a way to automate it. This is especially a problem as the number of devices becomes large. Internet connections can be spotty and there is no robust way to ensure that each step has executed for all devices.
It's prone to failure. Especially between steps 4 and 5 above. It seems there are little to no guarantees of when/if an update was successful to know definitively when to re-enable Single App Mode.
It fails for devices that are offline at time of update. If a device does not have internet connection when the update is executed, there is no way to guarantee that the steps execute fully and in the correct order the next time the device comes back online.
I am looking for a scalable solution to reliably update my managed, Single App Mode app running on thousands of devices in an automated way with no user interaction. I am using Meraki for an MDM right now, for what it's worth.
With iOS 11.2 you can now push a silent update to a device with it running SingleApp mode.
Apple failed to mention this to the public but is included in the beta notes.
Called Enterprise Support today, They could not find any official documentation mentioning ios 11.2.x supports the updating of apps while in single app mode :(
Now with iOS 11.3 beta it is working again but after updation, app is not automatically locking in Single App mode we have to restart device.
Hope in upcoming beta's this issue will get addressed.
iOS 13.1 beta 1 seems to fix most of the issues I have been having in this area.
I had seen issues in iOS 11-12.* where updates sometimes worked, but sometimes showed a pin-pad even though no passcode or guided access code was set, or otherwise behaved strangely.
In the 13.1 beta 1 you can push an App update and nothing will happen on the device, but if you send a restart command afterwards the device will restart, update the App and continue in single app mode.
I have tested with both 'Single App Mode' (SAM) and 'Autonomous Single App Mode' (ASAM) and it has worked every time for me so far.
This works for my use case as you can push the update anytime and schedule the restart at suitable time when the device is not in use.
edit: 13.1 beta 2/3/4 changes this, now when you push an update from your MDM the App will close, update and re-open and continue in single App mode. I checked both SAM and ASAM both now update without the need for a restart.
I experience an unpleasant problem for which I can't really find a conclusive reason: if I reprogram my BLE112 module (BLEBee from Michael Kroll / seeedstudio), for some reason the settings (especially the UUID keys to peripherals) are not being updated.
This is very unpleasant since that almost makes it impossible to connect to the device via iOS / Xcode.
Any leads on how to solve this and what would cause this issue?
Note: I reprogram them using CC Debugger and BLEUpdate from Bluegiga. I'm sure the values are in fact being reprogrammed, but iOS seems to keep the old info at least for some time.
(iOS 8 / Xcode 6 beta)
Have you tried to reset the settings of your phone? This is a common problem with iOS. Once you connected to the e.g. original firmware of the BLEBee and change the services and characteristics, iOS will show you the cached ones. Try to initially turn off Bluetooth, kill you app, restart BT and start your app again.
If this does not help Reset the Settings of your Phone.
Hope this helps,
Michael.
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.