I have an app on appstore that uses notifications.
Today I got a support message from a customer having problems..
I already noticed that sometimes when upgrading from iOS 4.x -> 5.x notification center didn't automatically allow the app to send notifications..
However in this case the user does not even see the app in the notification center list.. I cannot reproduce this problem but is there anyone who knows how to fix this or knows the cause of this problem?
Ok, after sending him some test cases it turned out that the app had to send a notifcation for it to appear in the list.. Wierd but the app now appears and works for the user..
Related
I'm developing an iPhone & Android via Phonegap. I already got the Push Function to work on the iOS device, and I also can recognise whether the user has Push activated or not while the App is running.
Now I want to be informed when the user activated / deactivated Push Messages in the notification center, even if the app is not running.
Is there anyway to do this? I searched quite a lot on this topic, but all I found were ways to recognise if push is activated or not, which I already can.
Any help will be appreciated.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
Problem:
The app doesn't appear on notification center and it is unable to receive push notifications right after installation completes and the app registers for push notifications via registerForRemoteNotificationTypes:.
Details:
The app usually appears in notification center after the device is restarted and after that everything works just fine.
Sometimes the app shows up in notification center right after intallation and registration for APNs(I still can't confirm this but I think I stumbled upon such situations).
The app calls the method registerForRemoteNotificationTypes each time a user logins and each time a user logouts respectively with bit masks (UIRemoteNotificationTypeAlert | UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound) and UIRemoteNotificationTypeNone.
enabledRemoteNotificationTypes returns correct values.
Initially I used the method unregisterForRemoteNotifications on logout but I changed it to registerForRemoteNotificationTypes:UIRemoteNotificationTypeNone due to suspicians that this could be causing the problem .
This problem occurs in both development and adhoc builds and irrespectively of whether the app is installed via xcode or itunes.
Any thoughts and advices will be greatly appreciated. Thank you!
This was happening to some of my devices. (Not showing up in notification center and not receiving pushes.)
Managed to fix it by doing:
Delete the app
Delete all the relevant profiles from the device. Settings app > General > Profiles, then tap into each of the Provisioning Profiles related to your app, then tap Remove. On iOS 8/9, where the setting no longer exists, use XCode > Windows > Devices > select device > Show provisioning profiles... > then remove the profile(s)
Turn your phone off, then on again.
Give 5 mins
Reinstall your app, the Provisioning Profile should get installed automatically.
Launch app and let it register and stuff.
Test push notifications again
For us, it didn't work immediately, so give it a few minutes.
Maybe there is a problem with registering and unregistering the app at login/logout respectively, from Apple's documentation:
An application should register every time it launches and give its provider the current token.
And not sure about unregistering, they don't mention unregistering in their programming guide, maybe the app should never unregister and the server should handle that, by sending or not sending push notifications depending if the user is logged in or not. This is how I've done it in the past, and never experienced this issue, so maybe this approach works for you too.
Well, I also have this problem, I found that as the application used the unregisterForRemoteNotifications before uninstall at the previous install.
And, in addition, if the application install again and login to register for the remote notifications, this problem will happen.
It happened also at the first install(installed after reset your iOS device). if you use the unregisterForRemoteNotifications before login, then register at the login operation, this problem will happen.
As this problem happened, you need to restart the iOS device.
For the unregisterForRemoteNotifications, we couldn't stop this problem, but we can reduce the probability of the occurrence of the problem, the method is:
If the device token didn't delete from provider at the previous install, then use unregisterForRemoteNotifications at the current install before login;
Otherwise, you should never use unregisterForRemoteNotifications.
I have registered an Custom URL scheme in my application. From server i send an SMS to the phone with the message starting with the custom URL scheme. example myapp://mymessageToApplication
When the SMS reaches the inbox, the messages application does not receognize the above message as a link. So, i am unable to click on the message to start by application. This happens everytime i delete the application and reinstall the application. But, when i restart my phone, the messages application recognizes the message as a link and i can click on the link to start my application. After that it all fine until i delete the current application and re-install it again through xCode on my test phone.
Does anyone aced similar issue? can anyone suggest me what could be wrong?
To add, i can type the message myapp://mymessageToApplication in browser to launch my application. It works always. So, the custom URL is registered fine. Only the messages application is not picking it up until i restart the phone.
I have filed a bug in Apple and they have replied for that. They ahve agreed that it is a known issue and they are working on it.
Below is the reply from them
This is a follow up to Bug ID# 10166363. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 10053369. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.
Thank you for submitting this bug report. We truly appreciate your assistance in helping us discover and isolate bugs.
Did you try to only kill and restart the messages application instead of restarting your iPhone completely?
I guess that's only because the Messages application only check which custom URL schemes are registered when it launches (and not when it is already launched but in background and is only brought to forground). Just a guess but it might be a probable explanation
(and if it is, I don't think there is anything you can do except file a bug to Apple... but check it first)
I have a strange problem with my iPhone app.
I use geolocation and push notification. Everything is ok, but I want to test from scratch on the iPhone (connected to xcode debugger)... and I can't re initialized the iPhone.
I explain: I remove the app from the iPhone, and after re-installing the app (with xcode or with iTunes), I launch the app, but iOS doesn't ask me to approve geolocation and push notification as it does the first time. In fact, it seems to 'remember' my choices.
As I need to debug this (Some users have problem on running app the first time), I'm blocked.
Thanks by advance for yours answers
There's a place in the Settings app to reset Location permissions.
I developed a application which uses push notification,it was working fine but when today i updated and when i run the application ,app is not able to get device token,both delegates methods are not called .but when i see the notification in settings of iphone ,i find my app as registered for notification ,how can i fix this problem any help?
Unlocked iPhones have many problems with Push Notifications. Check the web, there are some work arounds you can do to get it working. Strange that it worked before, but now it isn't.. The methods you spoke about are the correct methods and should be fired when launching the app...
You can try to kill the app from the multitasking. Maybe that's the case the methods aren't called...