Problem connecting

[Arieg007]

I press enter and it gives me the error below and won't let me continue pixel 9 pro xl

[yanirta]

Same here, will show this error after login attempt.

[KieronQuinn]

Please try again after updating to 1.0.2. If it's still not working, follow these steps:

• Return to the uTag landing page (with the Get Started button)
• Long press in the bottom right corner (may also be bottom left with a RTL language), you should see a message that developer options have been enabled
• Try to log in again. When the error is encountered, you should see a notification that an error has been captured.
• Tap the notification, and a dialog will open. Take a screenshot of the dialog, and press the copy button.
• Paste the copied output and send the screenshot here.

[iMongui]

Same here, not sure whats going on but cant login through agent web browser, i can login through mobile web browser normally but using the login process through the app nop

[KieronQuinn]

Same here, not sure whats going on but cant login through agent web browser, i can login through mobile web browser normally but using the login process through the app nop

Could you please try the steps in the reply above yours, I've not had a response from anyone with the information yet. I cannot fix something I cannot get data from.

[iMongui]

I've tried to tap on the notification but nothing happens, developing enabled before that, so not sure how to show that data

[uraldai]

First of all, thank you for the work you're doing!!

I have the same issue. I activate developer mode but nothing happens when the error message appears, nothing when clicking either on the message or the close button. No new notification pops up saying that an error has been captured.

Thanks in advance.

[KieronQuinn]

If you get no notification then you're seeing the same behaviour as a couple of people on the Discord. This means that the login return from the browser is sending data uTag either doesn't understand or is not valid. Since I don't control the login, this is unfortunately out of my control.

Those who have had the issue previously were able to log in after creating a new account. Is that the same for you all?

If you still cannot log in with a brand new account, please change the password of the new account to something generic and email me the credentials (address is on my website). Since it'll be a new account with nothing on it, that would allow me to work out what's going wrong.

Otherwise, there's nothing I can do about this issue.

[iMongui]

Tried with new account, tried with old account changing password, same behaviour... Im pretty sure its something very easy to fix but well, im not developer so all i can do is test and test and test, so if you dont mind, i can give you credentials in order to see if im making something wrong, how do you see it?

[KieronQuinn]

Send me an email to the address linked at https://kieronquinn.co.uk/

[yosef019]

תעדכן ל1.02 הכל עובד בואןפלוס 12 תתקין מחדש

[petertriho]

I had the same problem, turning off adblock worked for me

[KieronQuinn]

Those of you still with this issue, please check it's still happening and whether disabling any adblock or VPNs fixes it. It might just be a security check that's being failed.

[yosef019]

I press enter and it gives me the error below and won't let me continue pixel 9 pro xl

פתח בדפדפן כרום

[shaharad]

i had the same issue as described here. The only solution that worked for me was to sign out of my Samsung account and create a new one. Now it works. My only problem is re-assigning the tag to the new account..

[nttaihrs]

Is there any update on this? Non of the above mentioned solutions works on my Pixel 9

[KieronQuinn]

Nobody has donated an account with the issue, so no.

[nguyentritai2906]

I created an Samsung account today by connect it with my Gmail account and notice that SmartThings and uTag open 2 different URLs when sign in. Is it suppose to work like that?

[KieronQuinn]

I created an Samsung account today by connect it with my Gmail account and notice that SmartThings and uTag open 2 different URLs when sign in. Is it suppose to work like that?

Yes, they use two different login flows since SmartThings only requires auth for SmartThings but uTag needs multiple scopes

[nguyentritai2906]

Here are the 2 responses return after login in that I got:

SmartThings (https://account.samsung.com/accounts/ANDROIDSDK/signInGate?locale=en_US&svcParam=eyJjaGtEb051bSI6IjE...kYzQyMTU3OGIifQ%3D%3D&mode=N)

code: 526f0cba25702de27bb3fa1b3dbfa741
api_server_url: b799120ff10b4845926aabde3b43c4366f6147bf2e7d7b605520465e85b07622
auth_server_url: b799120ff10b4845926aabde3b43c4366f6147bf2e7d7b605520465e85b07622
code_expires_in: 300
state: 16d71b8c584bc96fa00456f7849c5f5921a844543b3d124714aeb733f2f7ff87
scope: iot.client mcs.client galaxystore.openapi
status: new

uTag (https://account.samsung.com/accounts/ANDROIDSDK/signInGate?locale=en-US-u-fw-mon-mu-celsius&svcParam=eyJjaGtEb0...hY2NlZTMzIn0%3D&mode=C)

code: e1ca8019ddb990d6a39071e7cccf57fdab15f15dde99d4991886c4819e126faf
api_server_url: b5388fce6e05c370ea54d7a898ae582e7fa3dcecc3f16fb76e67fb7b5f39d612
auth_server_url: b5388fce6e05c370ea54d7a898ae582e7fa3dcecc3f16fb76e67fb7b5f39d612
retValue: 11d6f0421a080a978d4a67c5f736a43e514113d0bc3c89f328c5f8266563c1ad
code_expires_in: 300
state: d6dd30a1cb84f4b6f589cc963805a7e183b297efc9821e771d4a0d918b1cb314
status: new

I notice for uTag, the scope is not included. Is this normal?

[KieronQuinn]

Here are the 2 responses return after login in that I got:

SmartThings (https://account.samsung.com/accounts/ANDROIDSDK/signInGate?locale=en_US&svcParam=eyJjaGtEb051bSI6IjE...kYzQyMTU3OGIifQ%3D%3D&mode=N)

code: 526f0cba25702de27bb3fa1b3dbfa741
api_server_url: b799120ff10b4845926aabde3b43c4366f6147bf2e7d7b605520465e85b07622
auth_server_url: b799120ff10b4845926aabde3b43c4366f6147bf2e7d7b605520465e85b07622
code_expires_in: 300
state: 16d71b8c584bc96fa00456f7849c5f5921a844543b3d124714aeb733f2f7ff87
scope: iot.client mcs.client galaxystore.openapi
status: new

uTag (https://account.samsung.com/accounts/ANDROIDSDK/signInGate?locale=en-US-u-fw-mon-mu-celsius&svcParam=eyJjaGtEb0...hY2NlZTMzIn0%3D&mode=C)

code: e1ca8019ddb990d6a39071e7cccf57fdab15f15dde99d4991886c4819e126faf
api_server_url: b5388fce6e05c370ea54d7a898ae582e7fa3dcecc3f16fb76e67fb7b5f39d612
auth_server_url: b5388fce6e05c370ea54d7a898ae582e7fa3dcecc3f16fb76e67fb7b5f39d612
retValue: 11d6f0421a080a978d4a67c5f736a43e514113d0bc3c89f328c5f8266563c1ad
code_expires_in: 300
state: d6dd30a1cb84f4b6f589cc963805a7e183b297efc9821e771d4a0d918b1cb314
status: new

I notice for uTag, the scope is not included. Is this normal?

This is expected, the scope is empty because it's doing an account login (which has no scope). If you're familiar with how Google's more widely documented login system works, the process is akin to doing an embedded setup and getting the AAS token.

Both of these responses are valid. The issue doesn't lie with the initial response, but with the later ones (or lack of them, if decryption is the cause).

[Jamousable]

Hello . Same problem on my pixel 7 . when I enable the developer mode and try to sign in again I don't get any notification tho .

[nguyentritai2906]

@Jamousable did you sign in by connecting it with your Gmail account?

[Jamousable]

@Jamousable did you sign in by connecting it with your Gmail account?

It works with google account. Thanks a lot .

[KieronQuinn]

1.0.6 contains some very minor changes related to how uTag handles country codes for the SmartThings APIs (aimed at solving the 1401 issue). Given the variation of locales that have this issue, could someone try that version to see if it's also fixed this issue?

[ewwachter]

I have version 1.0.6 with this issue and the only thing that solved was creating a new Samsung account. thanks @KieronQuinn!

[zzz17zzz]

I encountered the same error message and found a solution that worked (for me), although I had to delete and remake my Samsung account which not everyone will want to do (my account was old and I haven't had a Samsung since the S2 way back in the day).

How I got the issue:

• SmartThings signed in through both methods (password or google)
• Signing out of SmartThings and testing both login methods (password or google)

My solution:

1. Delete Samsung account completely
2. Recreate the account
3. Sign into SmartThings (using username/password, NOT Google login)
4. Attempt to sign in via uTag - this worked on the first try

Notes:

• I got no clue if the Google login would work since the password login worked immediately
• My original Samsung account was old and when I recreated it, my previous password no longer met their updated security requirements. Maybe there's a security/validation check? (Seems unlikely but worth flagging this just in case)
• uTag version was 1.0.6, SmartThings was 1.0.5, Pixel 8 Pro running Android 15

Hope this helps

[KieronQuinn]

@iMongui did you ever end up emailing? I've discovered that Squarespace has been eating some emails sent via my site so if you did, could you do so again via the address that's now linked on the same site?

I've had a good result with fixing the 1401 issue with account access so hopefully the same can be done here.

[mkashey]

I also have a Pixel 9 Pro XL. Just purchased GalaxySmartTag2 to use on a trip. Downloaded and installed Utag, I believe according to directions. Utag installed the modified version of SmartThings. I provided permissions and directed by the app. I signed into both accounts using the same email address. I opened SmartThings via the Utag app and tried to pair the app with the smarttags. I scanned the URL and turned on the smarttags. (to ensure I had the correct tag for the url). SmartThings did not find the tag and provided the error code. 05-300. Both tags beeped (to shut off I assume). I also tried restarting my phone, uninstalling both apps and reinstalling the Utag app. Am I doing something incorrectly? I am a tech novice. Bluetooth is on. Please help.

[KieronQuinn]

I also have a Pixel 9 Pro XL. Just purchased GalaxySmartTag2 to use on a trip. Downloaded and installed Utag, I believe according to directions. Utag installed the modified version of SmartThings. I provided permissions and directed by the app. I signed into both accounts using the same email address. I opened SmartThings via the Utag app and tried to pair the app with the smarttags. I scanned the URL and turned on the smarttags. (to ensure I had the correct tag for the url). SmartThings did not find the tag and provided the error code. 05-300. Both tags beeped (to shut off I assume). I also tried restarting my phone, uninstalling both apps and reinstalling the Utag app. Am I doing something incorrectly? I am a tech novice. Bluetooth is on. Please help.

This is covered in the frequently asked questions.

[Valnjes]

Have this error, cant sign in. In the Smart-Things APK im signed in. Can see all the devices, but cant sign to uTag, so i cant see the location of the devices.

I will try again tomorrow, maybe it will work. Maybe not.