-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auth token error upgrading from 1.9.9 -> 1.10.0 #1264
Comments
Saya my ledger on Google drive got corrupt it always happens when I've got trillions on it. Please assist |
hey @simonmcl the App Group is now required because we have released an upgraded Push sdk, keys and some session data now needs to be shared with the UNNotificationServiceExtension.
We will fix this in the next release but notice that Web3WalletClient exposes this publisher already |
I still meet this error in 1.8.4, can I use the SDK without an entitlement? I don't need this feature. |
Describe the bug
After migrating to 1.10.0 the socket fails to connect and the console is filled with:
After debugging it seems that setting up an App Group is now required? and required to be passed into
Networking.configure(groupIdentifier: "", projectId:....
. If this isn't done it fails to connect. Why is this now required? Its also not explained or detailed in the project repoAlso note many of the links in the README are broken
Semi-unrelated. I've noticed that 1.10 adds a
pairingDeletePublisher
i've been waiting for this to help diagnose an issue. But i'm confused how to access it? Its not available onPair.instance
andSign.instance.pairingClient.pairingDeletePublisher
returns an error due topairingClient
being private. How do I access this?SDK Version
The text was updated successfully, but these errors were encountered: