[IOS] Protected data not available yet. Retry operation
See original GitHub issueWe started to get a lot of Protected data not available yet. Retry operation
from our ios users.
It is happening for ios users above 14.6 while the majority of the problems come from ios 15.x. Does anyone know what could be causing the problem? We’re on 6.0.0-alpha.9
Issue Analytics
- State:
- Created 2 years ago
- Comments:10
Top Results From Across the Web
iOS 15 beta wipes out app data | Apple Developer Forums
the app data is getting wiped out (UserDefaults, keychain password). I'm on iOS 15 public beta 3. Has anyone faced similar issue, or...
Read more >swift - iOS - retry mechanism - Stack Overflow
So i have managed find the problem. The retry func works fine but it repeats because i dont stop the timer in refreshSession...
Read more >Microsoft Intune App SDK for iOS developer guide
Specifies whether the app will warn the user during launch if the app does not have an Intune app protection policy. Note: Users...
Read more >Retry asynchronous functions | Cloud Functions for Firebase
When retries are not enabled for a function, which is the default, the function always reports that it executed successfully, and 200 OK...
Read more >Common errors while enrolling iOS devices using Apple ...
Make sure that you complete updating the device to iOS 11 before adding the device to DEP. 5. A cloud configuration is already...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not really, we reduced our number of concurrent async operations which reduced the occurrences. But they still occur.