question avatar image asked

orphaned account (?) leaves QA unable to frictionlessly log in

Before I asked my previous question about the best way to test the new user experience, my colleague had already attempted unlinking device IDs and deleting players to simulate the new user experience. Now, when they boot any android build, their frictionless login is rejected

Playfab Error: ServiceUnavailable
HttpCode=400, HttpStatus=BadRequest
ErrorMessage: 409 Conflict
EndPoint: /Client/LoginWithAndroidDeviceID

It's been like this for a few weeks, and I was hoping that whatever was blocking the request would clear out, but it still seems broken.

I'm hoping someone from playfab can go in and clear out the blockage? Or let me know if there's a way for me to do this myself.

The Android ID being blocked is 56d605ba04cc117c, and the title ID is 80CD.

I think there's one other device affected, and I'll update this question if I get more info.

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

brendan avatar image
brendan answered

Can you clarify the test case? The only time you should be encountering the ServiceUnavailable/Conflict issue is if you have multiple calls in flight for the same account at the same time (so, in this case, multiple testers trying to use the same account to sign in at the same time, generally).

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total. avatar image commented ·

The tester is just booting the game. There's no output in the log that implies we're trying to do two things at once - just frictionless login, then this error. It's using the android ID so couldn't be two different devices.

0 Likes 0 · avatar image commented ·

...but are you implying that if, say, two devices shared an account using google login, they couldn't both log in at the same time? That's not happening here, I just want to make sure we're covering that test case if necessary.

0 Likes 0 ·
brendan avatar image brendan ♦♦ commented ·

If they're trying to sign into the account in the same millisecond, yes, that could cause an issue. As you can imagine, that should be rare. Are you seeing the issue now for the Title ID and PlayFab ID listed? If you don't mind, we can do some testing against it, to see what we can see.

1 Like 1 · avatar image brendan ♦♦ commented ·

I won't worry about milliseconds then. that's the android ID, not playfab ID, but yeah. any help greatly appreciated. I can't get a playfab ID because it refuses to sign in with the android ID.

0 Likes 0 ·
Show more comments avatar image commented ·

> Can you re-test?

Retested and still the same 409 error. It's been over a month now I think.

0 Likes 0 ·
brendan avatar image brendan ♦♦ commented ·

Ah, if it's been that long, it's clearly stuck due to corrupt data. I had a look at the records and removed the Android ID entry once I confirmed the User account had been cleaned up. You should be good, now.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Error rendering WebPanel (widgets/consolidation-widget.ftl): org.hibernate.hql.internal.ast.QuerySyntaxException: AvailableConsolidation is not mapped [from AvailableConsolidation up where up.node = :node]