I have a service worker running in production, lately I have started seeing increase in error Failed to get navigation preload state: The user denied permission to use Service Worker. This error was always logged on our end but the amount has been quadrupled in past 3 weeks. I am not sure what causes this error at the first place, and I have tried multiple ways but could not able to reproduce. Most of these errors are coming from recently released Chrome 105, but I did not saw any policy change in the new release which can trigger this.
I am looking for more details about the error? What causes it? How it can be reproduced?
Related
I am utilising the Template App, provided by MongoDB Realm, available here: https://www.mongodb.com/docs/atlas/app-services/reference/template-apps/ (swiftui.todo.flex).
I am using SwiftUI, with Swift.
The app works correctly, apart from one aspect - when I log in as 'User 1' (arbitrary reference) it is successful - then, if I log out, and log back in (on the same device - i.e. the iOS simulator) as 'User 2', the login is successful but then I receive a recurring error message which reads 'Automatic Client Reset Failed' and the code eventually crashes with the following:
Received: ERROR "User mismatch for client file identifier (IDENT)"
(error_code=223, try_again=true, error_action=ClientReset)
libc++abi: terminating with uncaught exception of type realm::MultipleSyncAgents: Multiple sync agents attempted to join the
same session
Realm documentation states the 'Multiple User Systems' is compatible with their product, and that there should be no issues operating multiple users on the same device.
Realm logs show a "ClientFileUserMismatch Error". I suspect that the app is trying to open the pre-existing Realm file using the new user's credentials, which is causing the error? But I'm unsure of how to resolve this - and I'm surprised that this error appears in their template code?
Can anyone assist me please?
I am running into a strange problem where the user was able to log in previously and now getting error 13 - Temporary password has expired and must be reset by an administrator. However, switching to a different device using the app login succeeds. Any ideas what needs to be done to clear cache or keys or anything else that is needed?
I have an iOS Swift project using the AWSMobileClient SDK (v2.9.9) installed with Cocoapods.
There is one problematic method that is used quite frequently in the app:
AWSMobileClient.sharedInstance().getAWSCredentials { (credentials, error) in ... }
and there is a specific fatal error that occurs:
Obtaining an identity id in another thread failed or didn't complete
within 5 seconds.
On some devices, it works fine 90% of the time and only usually occurs after a sequence of steps - e.g. sign in, log out, sign in again (the method is called after sign in).
However, recently on a new device that I've been testing on it has appeared every single time.
There was another Stack question here that suggested that another AWS SDK operation may be running in parallel when getAWSCredentials is called - but after reviewing my code I'm fairly sure this isn't the case.
I've also tried running this method on the failing device to see if it would give any clues:
AWSMobileClient.sharedInstance().getIdentityId().continueWith { task -> Any? in ... }
and returns with this error:
Fetching identity id on another thread failed. Please retry by calling
getIdentityId() method.
I've spent hours looking through my own code and the stack traces that led to the error and am at a dead end with thoughts on how to solve or even debug this further.
Hopefully someone will be able to suggest something to help me - thanks! :)
I've created an interaction in maximo 7.6 and when I try to run it, I get this error message:
BMXAA1481E - Cannot deliver the message to the endpoint. Internal
Error
I've tried fixing it, but nothing works, does anyone how to fix this or even why does it pop up?
I have an app that uses pushkit (voip push).
Most of the time the pushes get through. But when there is a lot of traffic, the pushes don't get through to the app.
I am in a state where I can somehow reproduce the error.
I used the extended logging from here:
https://developer.apple.com/library/ios/technotes/tn2265/_index.html
And I found this to examine the logging:
http://iosdevelopertips.com/core-services/debug-failed-push-messages-by-logging-apsd-process.html
Still, I got two different cases, where I just don't get further:
- In the apsd-log I get
Received message for enabled topic ...
and in the app the didReceiveIncomingPushWithPayload is not called. I produce a log entry right at the start of the function and do nothing special that could prevent the function from finishing.
- In the apsd-log I get
Stream error occurred ...
but do not find any other error messages, why this error occurs.
The Port seems ok
After restarting the app the pushes get through again.
EDIT:
The relevant error in the log file seems to be:
apsd[82]: Failed sending message to client: com.apple.telephonyutilities.callservicesdaemon.voip.push.development
There seems to be two types of cases: In some cases, which are reproducable with large traffic, reregistering the pushkit seems to help.
In other cases, which occur random, it simply does not. Restarting the app does not help here either.
All helps so far, is restarting the iphone.
EDIT:
I am still struggling with this problem.
In some cases I get a memory warning before the push seems to fail.
In other cases I get a xpc communication warning like this:
SpringBoard[43] <Warning>: Communications error: <OS_xpc_error: <error: 0x3b7ef614> { count = 1, contents =
"XPCErrorDescription" => <string: 0x3b7ef86c> { length = 22, contents = "Connection interrupted" }
}>
In some cases none of the above happens, but push still does not work.
EDIT:
In developer archive I found this very interesting thread, but still no answer:
https://devforums.apple.com/thread/257354?start=50&tstart=0
Does anybody know if there is a connection between xpc and push?
And is there a way to detect a xpc error in code?