Does anyone else have troubles with silent push notifications on iOS 14 (latest beta). We use silent PNs for some sort of minimal syncing between devices via backend, and it works well on all iOS versions except iOS 14. I wrote "doesn't work properly" because sometimes they do work, but usually they are not delivered to iOS devices (response code from Apple while sending them is 200, means everything is ok).
UPD: seems like it's iOS issue, and also seems like it's fixed in iOS 14.2
I experiencing same issue and this is critical for my app (I use silent pushes while in foreground to deliver messages to user)
I just installed iOS 14.2 beta and silent pushes work ok there (bug fixed). So looks like this is iOS 14.0 bug and apple knows about it and fixed already in beta.
Related
I have an app in Android and iOS that uses Sinch videocalls but since the iOS 13 launching the video the iOS 13 sends is bad, it looks like static. I've discovered that if during the videocall I use the iPhone in landscape orientation the video transmitted is normal. This problem happens even with the sinch demo. Any ideas to solve this?
I've tried: use multiple connections, updating the framework to the last version, in multiple devices, modifiy the frame from the callAsyncLocalVideoFrameHandler.
I expect to be able to send good video from devices with iOS 13 of higher and iPadOS.
we are aware of the issue, it's caused by a compatibility issue between iOS 13's H264 Codec and the WebRTC version we use on our SDK.
We are working to fix that. There will be a new major iOS SDK release to support iOS 13, at the moment we do not recommend customers to release new versions of their apps with iOS 13/Xcode 11 support.
Your current apps will still work on devices running iOS <12 and the new iOS 13, as long as they are not built with XCode 11.
iOS 13 brings also new directives to use VoIP Push on Apple devices, this will also cause changes on how customers integrate any VoIP SDK, if you use VoIP Push notifications.
See note and links on our website.
https://www.sinch.com/docs/resources/downloads/index_vvv.html#info-ios-13-voip-push-changes
Jorge Siqueira - Sinch Voice & Video.
I also see problems with iOS 13 and Sinch Video call. I have tried to go back and build with Xcode 10.3 but that does not help either. iOS 12 still works like you say
In iOS 11, no CloudKit record change notifications are received when the app is in Single App Mode (SAM) or Guided Access Mode (GAM).
The foreground app would be receiving silent notifications just fine and updating the UI, but once I put it in GAM or SAM, didReceiveRemoteNotification is not called (neither the background method nor the older foreground-only method).
I have an iOS 9 iPad in Single App Mode (SAM) that receives all the CloudKit notifications, and I remember my iOS 10 iPad also worked, so this is an iOS 11 issue.
I wonder if Apple is disabling push notifications in general if a device is in SAM or GAM?
This appears to be fixed in the newest iOS 11.2.5 beta 4. Will wait for the GM release of 11.2.5. Thanks!
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.
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.
I have developed IOS app and it is published in app store. When i am sending push notification from back end (using php script) only iphone5 & iphone5s users are getting the notification. Both of these phones are having IOS 8 installed.
iphone6 & iphone6+ devices not receiving any push notifications, all my devices are having same ios version 'ios8.1.3'. I also updated iphone6+ to ios 8.2 but nothing.
I have tried various things such as resetting the notification dialogue etc.. but nothing has helped so far.
Is there any solution for this problem.
Thanks in advance.