I suddenly started having problems receiving push notifications to my application targeting iOS 9.0+ yesterday - now they're working fine again without a single code line change in the app or on the notifications provider server (anyone happened to witness the same? / to know if Apple might have had some kind of APN services outage yesterday?)
Anyway, I tried debugging the problem using the steps described here: https://developer.apple.com/library/ios/technotes/tn2265/_index.html#//apple_ref/doc/uid/DTS40010376-CH1-TNTAG24 in the Enabling Push Status Messages on iOS section but I was unable to install the "APS/PC Logging" tool to my iPhone 6s / iOS 9.3.1 - I sent the provided file PersistentConnectionLogging.mobileconfig to the iPhone via an email attachment as suggested but when I tried to open it, I received an "Invalid Profile" error message.
Hence my questions: Is it possible to install the "APS/PC Logging" tool to iPhone 6s / iOS 9 and debug push notification logs that way?
(according to the Document Revision History, the last modification in the Apple document linked above was made on 2014-10-01, i.e. before iOS 9 was launched so the instructions and/or the file might be outdated).
Thank you very much in advance for any answer!
Got back to this issue after a longer while and I'm glad to find out that even though nobody answered the question here, there's been an update made to the "Troubleshooting Push Notifications" technical note available at https://developer.apple.com/library/content/technotes/tn2265/_index.html#//apple_ref/doc/uid/DTS40010376-CH1-TNTAG24
According to the Document Revision History, there have been several modifications described as "Updated for iOS 8 and later. Refreshed logging profile." dated a couple of days after I asked my question here. I downloaded the new version of the tn2265_PersistentConnectionLogging.zip file and can confirm that it is now possible to install the tool into an iPhone running iOS 9.3.4 and capture some logs.
(Not sure if my question could have triggered the update or if it was merely a lucky coincidence - anyway, I'm glad that it's working again.)
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 have an app in the App Store with an Apple Watch app. For most users, installation works fine.
Some users have had a problem where the Apple Watch app installation fails at what appears to be 75% (based on the pie graph status indicator over the app icon on the Apple Watch). Out of these users, many of them have eventually been able to get it to install after rebooting both the Apple Watch and paired iPhone a few times or updating the software on both.
At least one person has not been able to resolve the installation issue. He has gone to great lengths troubleshooting, including erasing and restoring his iPhone Apple Watch multiple times. All the other Apple Watch apps that are part of iPhone apps on his phone get automatically installed, except for mine, which fails.
Is there anything I might be able to do as a developer to troubleshoot the failing installation further, and possibly change about my app to make the installation process more reliable?
I've talked to a number of other developers about this, and they all seem to think it must be a bug in iOS or watchOS that I don't have any control over as a developer, but I really want to help this guy out who is having trouble installing my app so I thought I'd post here to try to get more feedback on what's happening.
I always try to post at least some code or log output in my questions, but unfortunately in this case don't really have any relevant code or logs related to this issue since it's all during the installation process.
After PetahChristian's comment on my question, I asked the person with the installation issue to download XCode and check the device's console log. Here is the relevant line from the console output:
Jun 16 10:44:40 WeeFee appconduitd[1843] <Error>: 0x16e12f000 -[ACXServerInstallOperation receivedDictionaryOrData:]: 524: Got error 17 in install done from remote side (MI error DeviceOSVersionTooLow ; Extended 0x0 ; Desc The system version is lower than the minimum OS version specified for bundle at /private/var/mobile/Library/Caches/com.apple.mobile.installd.staging/temp.eMUVkq/extracted/Payload/Pee and See Watch.app. Have 2.1; need 2.2)
Even though I had asked this person if he had iOS and watchOS up to date, and he told me he did, it turns out he didn't. And, Apple seems to just let the installation fail without showing the user an error message about software updates being required to run the app. Once he actually did update watchOS, everything worked fine with the installation.
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....
Our new IOS app was updated to Appstore successful yesterday.
Some users can update normally but the others not.
Include myself, we can see Appstore is downloading our app,so do the icon on desktop.
But when downloaded the icon of our app disappear.
It seems that the app was not installed.
Some 6 and 6s users have this question.
Our app is passed by Appstore, and some user can download and install it.
The package seems worked.
Why the app can not be installed in some users' IPHONE?
Finally catch the problem.
Because of the pool network, we retried a few times updating the package.
At the last time, we choose the wrong package with lower version code in Info.plist.
The package had a lower code, but may apple keep a higher version code for verification.
We get a lot of 1stars caused by this which made us upset.
I don't understand why Apple put it to AppStore in such a case.
Anyway, please be careful at package updating.
No issues with you code as well as your package info. Yesterday Apple had issue with their server.
Refer this link for more info.
If app is installed without any issue & in some device its not than there might be few possible reasons like below:
First possible reason is Minimum IOS version set in the App is higher than the device OS version. Let say for ex: In your App you have set the Minimum iOS version to 9.0. And users who are not able to install will running of less than 9.0.
Second possible reason is Architecture support. May be your app not supporting arm 64 support & due to that it will not allowing to install on arm64 based devices.
Now in your case i strongly believe there will be minimum iOS version issue. Why less chances of second issue is as you know now arm64 support is compulsory in iOS Apps. Otherwise Apple will reject your app.
I hope this will help you.
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?