From the ios developer doc, I found that an iOS app could support maximum of 64 local notifications.
( somewhere in stackoverflow I found it's maximum limit is 128 ).
So, I made an app scheduling 300 UILocalNotifications.
Xcode 5.1 compiled my code scheduling all 300 notifications.
I used NSLog() to verify this.
NSLog(#"\nLocal notifications count is::%d",[[UIApplication sharedApplication] scheduledLocalNotifications].count);
And then I began testing.
I observed notifications over 150.
So, how's this possible?
But I had an issue. When I clicked on my app, it displayed an alert : "NotificationTestingApp" is No Longer Available
Can somebody explain this?
Thanks.
Related
I've implemented notifications extension and now try to debug my code, but without any success.
I tried several approaches how to handle it, for example stackoverflow question
When I "attach to process ...", I just see "waiting to attach" message on desired process. If I send push notification to invoke my extension, it just crashes
Message from debugger: Terminated due to signal 9
Is it possible that OS just close my extension, because it uses to much memory or it has too big size (~.appex = 20mb), but I can't find guidelines about extension size/number of files, etc.
Any suggestions, help?
Thx in advance
It seems like that there is a memory limit for Notification Service Extension. Someone said it may be 5mb. And someone said that the limit is 5mb in ObjC, or 15mb in Swift.
Due to the limit, I remove all 3rd party libraries in Notification Service Extension.
I disabled the address sanitizer and undefined behavior sanitizer in the main app's scheme and the service extension loads ok now.
I have checked Notification Service Extension, Here you can see what is memory limit as per latest iOS update.
As per Xcode debugging 24 MB is notification extension memory limit.
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 am using local notifications in my app.
Now that iOS 11 is out there they are not working anymore. I haven't seen anything that could cause this in the release docs, does anyone know what could be causing this?
I know it's deprecated but i see no reason why it shouldn't just work anyway.
Thanks in advance
It seems there is a bug in iOS11. I can see if I schedule more than the 64 allowed notifications it ignores all the notifications I schedule.
The docs state the system keeps the soonest firing 64 notifications and discards the rest. On iOS11 it just discards them all...
So the fix in my case was to make dead-sure not to schedule more than 64 notifications.
I've got a project I'm working on which uses VOIP notifications to "wake up" apps that have been put into background/terminated. These notifications are sent periodically, and everything seemed to work fine until recent iOS updates.
It appears that after a certain amount of time in which the app has been in the background (happens to some users after 5 minutes, others after 20), the devices no longer process any code after receiving the voip notifications.
I've read a bit in apple dev forums and some other devs are running into similar issues, all speculate if its related to the new iOS updates (10.3.1/10.3.2).
Has anyone else run into this issue, and if so, have you been able to solve it?
Thanks!
This is the new normal on latest iOS versions.
You should begin to use push notifications.
Here is a guide from Apple.
What ended up seeming to be the fix was updating to a newer version of socketio library.
You can try debugging your app in background or in kill state ( terminated state ), so you can get to know that payload from pushkit comes or not or possibly some crash at iOS code end.
Debug pushkit notification in terminated state
Put debug pointer on delegate methods
Go to edit scheme
Select run option then Launch -> Wait for executable to be launched
Send push kit payload from back end
Once you get payload on device
it will automatically invoke and debug pointer will invoke at delegate methods.
Refer
I have a problem with voip push notifications not arriving sometimes to the app delegate and I want to track where the problem is.
I enabled push logging on the device as described in Apple's technical note from here:
https://developer.apple.com/library/ios/technotes/tn2265/_index.html#//apple_ref/doc/uid/DTS40010376-CH1-TNTAG23
I sent few push notifications (which arrived) to test the logs but there are no logs containing any push notification info in
/Users/[username]/Library/Logs/CrashReporter/MobileDevice/<devicename>/PersistentConnection/
..folder containing my app bundle identifier nor anything with apsd (I tried both spotlight and manually search files).
I see documentation was updated last time 2014-10-01, after iOS 8 was released and I wonder if it is outdated anyway? I see small note:
Note: On iOS 6.x, push logs will not be written to the device console.
They are only available by syncing the device with iTunes (r.
12575868).
Is this also the case with iOS 7 and 8?
Which files should I look into (there are plenty of files updated in PersistenConnection folder every time I connect device by cable)?
What am I doing wrong? Is there a more convenient / automated tool to collect this type of logs?