Why I'm getting duplicate push notifications on iOS 9? - ios

I am receiving the same push notification twice in iOS 9, but It is working fine in iOS 8.
The problem still persists after updating the iOS version to 9.1, 9.2.
The application is generating new device tokens every time the app gets uninstalled and re-installed.
I found a solution which suggested to keep the latest device token id tagged with the user and remove all the previously tagged device token's, but I want my user to log in to the app from multiple devices (like an iPad & an iPhone) so I can't follow the solution.
Any possible solution/tips to handle this issue ?

I think you should use keychain to store or update device tokens. It can't be removed when application is uninstalled.

Related

Firebase Cloud Messaging issues / changes with iOS 10.3

I have an app that I am building and prior to 10.3, the push notifications worked perfectly.
When 10.3 was released the whole Firebase tool set seemed to break for a couple of weeks until Google updated the PODs for the Framework.
Once done, I started again to play with this, but even though the previous code to push notifications worked to the previous build of the app the version built with 10.3 doesn't see any messages.
If I user NWPusher to push messages using the APN direct then I get messages fine, but the ones that were and still are working to the older version of the app don't get seen in the app / on screen / or in the debug window when connected to XCODE.
Has anyone had similar issues?
The code is unchanged from the version that previously worked and the direct push via APN works as well? Thanks in advance.

Is registerForRemoteNotificationTypes still working on ios 10?

It is quite related to this problem.
Building for iOS if registerForRemoteNotificationTypes: is not supported in iOS 8.0 and later
For all my latest app, I have already changed the way app register push token.
But I have very old app (in 2014). It just use registerForRemoteNotificationTypes. I notice that device can't register push token already.(it is on app store since 2014)
Is that correct behaviour? Do I have to update my app? I thought apple would still support for backward compatibility.

How can I make allow users with older versions of iOS to download an older version of my app

I've updated my app and due to some of the functions I'm releasing it has to be for iOS 10 and up. I understand that there is a way for users that have not upgraded to iOS 10 to be able to get the older version of my app but I haven't been able to figure out how to enable that in the app store. I just tested on a device and currently if you have iOS 9 it will tell you that you can't get the app because it is only supported on iOS 10. No option to download the previous version.
According to the redit article below Apple enabled the behavior I want. I just don't know how to turn it on for my app.
https://www.reddit.com/r/apple/comments/1mjw36/people_with_old_ios_devices_you_can_now_install/
So to update everyone: This only works if the app is already purchase. All new purchases will force to upgrade to the latest OS.
I think this feature just works if you already purchased the app and want to reinstall it.
A solution would be to purchase the app on your Mac and then try again on the iOS device.
Here is an article about it: https://sites.google.com/site/appleclubfhs/support/advice-and-articles/app-store-downloading-older-versions-of-apps-ios

updating my app to only support iOS 4.3+, what happens to users running iOS < 4.3?

This seems like a question that should have a lot of answers on Google, but I can not find an answer to this....
I am updating my app to only support iOS 4.3 or later. What happens to users that currently have my app installed and are using iOS < 4.3. Does the app remain installed on their devices and they are just not eligible for updates?
They will not be able to update the app, I believe there will then be a permanent "1" on the AppStore icon. If the user downloads the update in their desktop iTunes, it will overwrite the old version and they'll never be able to install that version on their devices.
As long as they don't restore their iOS (wipe the phone) the app will remain.
EDIT:
There is no reason now to support "4.3+". Any device that canrun 4.3+ can run 5.0+, and any device that can run 5.0+ can run 6.0+.
Staying under 4.3 for iPhone 3G is fine, but if you now support 4.3+ you've really gained nothing other than alienating iPhone 3G users for no benefit.
In other words, users who are still on 4.3 are probably not the type of users who are updating apps from the App Store anyway.

How can AppStore apps stop supporting ios4?

I have a app on App Store supporting IOS4+ device. However, I really wanted to use some new API feature in ios5 and decided to bump my base SDK to IOS5.
My questions is, what is the setting needed on iTunesConnect? Does Apple allow me to do this? What will happen to those clients running my app on IOS4? Will they just stop receiving update notification from app store?
If Apple forbidden the change, what is the best option for me? I don't want to make another app which has the same interface/functionality but with only iOS5+ device support..
All you need to do is update your project by setting the Deployment Target to your new minimum version. In this case, set the Deployment Target to iOS 5.0 or 5.1. Build and test. When your app is approved, it will only be usable on devices with the version of iOS you selected, or later.
Existing users still on iOS 4 will still be able to use their existing app. But they can't install any further updates.

Resources