Krypton iOS needs to be foreground in iOS 14

[halostatue]

Since I’ve upgraded to iOS 14, I’ve found that I need to have Krypton in the foreground with the phone unlocked to either be able to sign commits or authorize SSH signatures.

This may be related to know iOS security/privacy measures, but it’s making Krypton substantially less useful for me.

[zobo]

I spent the better part of the last 4 hours digging into this as it also bothers me a lot. The conclusion I came to is that as part of the pairing process, the iOS device does not send back SNSEndpointARN field (empty). The cause could be:

1. Due to iOS 14 updates the delegate does not get called func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) { I found some clues as to how things might have changed on iOS 14: https://medium.com/@prafullkumar77/how-to-handle-push-notifications-in-swiftuis-new-app-lifecycle-7532c21d32d7.
2. The updateSNS somehow fails.

I have a working iOS development environment now and perhaps I'll try to do a debug build in the next days.

[halostatue]

I’ve had to remove Krypton from my workflow for the time being because of this, so best of luck.

[zobo]

I have made an AWS test if it's still possible to register SNS Platform Endpoint and that seems to work ok. So I think I can reduce it to a problem, that the application does not get the Remote Notifications Device Token. I tried to build the iOS app on my Mac, but the iOS development process is a real pain and I was not yet able to do that to at least enable debug logging... At least one dependency also needs to be updated (https://github.com/aschuch/AwesomeCache/pull/114). I hope @agrinman will be willing to release an update...

[zobo]

It ended up being an issue with my phone. Removing and installing the app again made it work.

[dmytroleonenko]

Works well for me as well. Seems not to be a krypton issue