[Bug]: Call to 'login' fails with 'incorrect UUID length' error #1913
Comments
|
Hello @AndreasBoehm thank you for reaching out! We're investigating this and will get back to you as soon as possible. |
|
Hi @AndreasBoehm, sorry for the delay in following up. I see in your logs you have these two lines that is the error response from the server: That is the server response so before that, there should be logged the actual POST request that will looks something like this: Do you have that information? |
|
Anyone have solution on above issue? please help... |
|
@AndreasBoehm @sw-tt-jigarkumarpatel we have made a number of improves to the SDK around this code. Can you try the latest SDK (5.1.8 at the time of writing) and let us know if it fixes it for you? |
|
@jkasten2 I am running into this issue on 5.1.14. At one point today I got 1 IAM to show at app start up (should show every time, but since then nothing. Here is a bit of log: Any additional information would be helpful!
SDK 5.1.14 Kotlin 1.9.22 Android API 34 |
|
@chrisagay do you use identity verification? Apparently, it is not supported yet in v5.x.x even though the method is there... I spend so much time trying to figure this out! |
|
I am closing my issue now as we are planning to move to a different platform and stick to OneSignal 4.X for now. |
|
I figured out my issue, we were calling initWithContext mulitple times with
different appId. Our iOS team has access to the setAppId() which can be
called after initWithLaunchOptions(), which also matches 4.x.x.
After adjusting to call initWithContext() once resolved the issue, but it
would be nice to be able to set the app ID separately and/or switch app
id's.
…On Wed, Jun 12, 2024, 11:35 PM Andreas Böhm ***@***.***> wrote:
I am closing my issue now as we are planning to move to a different
platform and stick to OneSignal 4.X for now.
—
Reply to this email directly, view it on GitHub
<#1913 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZEBVZ6A66YQCZYOSRP7LDZHE4UFAVCNFSM6AAAAAA7NWEXZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGYZDAMBYG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I should also note I had to clear my data
…On Thu, Jun 13, 2024, 6:02 AM Christopher Gay ***@***.***> wrote:
I figured out my issue, we were calling initWithContext mulitple times
with different appId. Our iOS team has access to the setAppId() which can
be called after initWithLaunchOptions(), which also matches 4.x.x.
After adjusting to call initWithContext() once resolved the issue, but it
would be nice to be able to set the app ID separately and/or switch app
id's.
On Wed, Jun 12, 2024, 11:35 PM Andreas Böhm ***@***.***>
wrote:
> I am closing my issue now as we are planning to move to a different
> platform and stick to OneSignal 4.X for now.
>
> —
> Reply to this email directly, view it on GitHub
> <#1913 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ADZEBVZ6A66YQCZYOSRP7LDZHE4UFAVCNFSM6AAAAAA7NWEXZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGYZDAMBYG4>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
What happened?
Can't receive push notifications because my user is not properly registered in the onesignal backend.
Steps to reproduce?
What did you expect to happen?
I did expect the login to work
OneSignal Android SDK version
Release 5.0.4
Android version
13
Specific Android models
No response
Relevant log output
[main] login(externalId: 1e8b0e2b-7feb-4dfd-xxxx-f7fd813433c7, jwtBearerToken: null) [main] OperationRepo.enqueue(operation: {"name":"refresh-user","appId":"4e3455d0-10a6-xxxx-bc85-3f4afea449fd","onesignalId":"local-0f3285db-xxxx-4b0d-8392-89c440f24d18"}, flush: true) HttpClient: Request timed out: apps/4e3455d0-10a6-xxxx-bc85-3f4afea449fd/android_params.js kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 65000 ms at kotlinx.coroutines.TimeoutKt.TimeoutCancellationException(Timeout.kt:191) at kotlinx.coroutines.TimeoutCoroutine.run(Timeout.kt:159) at kotlinx.coroutines.EventLoopImplBase$DelayedRunnableTask.run(EventLoop.common.kt:501) at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:280) at kotlinx.coroutines.DefaultExecutor.run(DefaultExecutor.kt:109) at java.lang.Thread.run(Thread.java:1012) [Thread-12] Failed to get Android parameters, trying again in 30 seconds. [Thread-12] ParamsBackendService.fetchParams(appId: 4e3455d0-10a6-xxxx-bc85-3f4afea449fd, subscriptionId: null) [DefaultDispatcher-worker-8] HttpClient: GET apps/4e3455d0-10a6-xxxx-bc85-3f4afea449fd/android_params.js [DefaultDispatcher-worker-8] HttpClient: Adding header if-none-match: W/"d022feffd55d242859d590b4f28e5690" [DefaultDispatcher-worker-1] HttpClient: GET apps/4e3455d0-10a6-xxxx-bc85-3f4afea449fd/android_params.js - Using Cached response due to 304: {"awl_list":{},"android_sender_id":"729718451091","chnl_lst":[],"enterp":true,"outcomes":{"direct":{"enabled":true},"indirect":{"notification_attribution":{"minutes_since_displayed":60,"limit":10},"enabled":true},"unattributed":{"enabled":true}},"receive_receipts_enable":true} [DefaultDispatcher-worker-5] HttpClient: POST apps/4e3455d0-10a6-xxxx-bc85-3f4afea449fd/users - FAILED STATUS: 400 [DefaultDispatcher-worker-5] HttpClient: POST RECEIVED JSON: {"errors":[{"title":"uuid: incorrect UUID length 42 in string \"local-df3ea23b-ff99-466a-84f1-71dd5ddb46a5\""}]} [OpRepo] OperationRepo: execute response = FAIL_NORETRY Operation execution failed without retry: [{"name":"login-user","appId":"4e3455d0-10a6-xxxx-bc85-3f4afea449fd","onesignalId":"local-7e897fc6-ef40-4734-bb71-1eac1949b680","id":"4d42a1c0-b434-4cde-b1e7-8e2b7cf5b63e"}, {"name":"transfer-subscription","appId":"4e3455d0-10a6-xxxx-bc85-3f4afea449fd","subscriptionId":"local-df3ea23b-ff99-466a-84f1-71dd5ddb46a5","onesignalId":"local-7e897fc6-ef40-4734-bb71-1eac1949b680","id":"17513b7e-cfec-4fc0-a954-891337a865e5"}]Code of Conduct
The text was updated successfully, but these errors were encountered: