Account creation on the hardware

[RobertKarp]

Hi,

We have finally been able to make packages for our title, but when trying to test these on the hardware we have found that not only do the old user accounts that we had on the kits not work anymore, but we are also unable to create new ones. Please could you advise?

Thanks, Robert

[jake-ruyi]

Servers are down. We didn't send out a notice because we hoped we have them back up before anyone noticed. So much for that... They're still down and we don't yet have an ETA. Sorry for the inconvenience.

[RobertKarp]

Hi Jake, No problem, thanks for letting me know. Please can you update once fixed. Thanks, Robert

[RobertKarp]

Hi Jake, Hope you had a good weekend. Just wanted to touch base and see if there was any progress on this?

[jake-ruyi]

We can't commit to a clear date because it's something out of our hands. That said, there's a chance we will be back up and running the end of this week or the beginning of next.

[RobertKarp]

Hi Jake, Sorry i've not been in touch, is there any update on this? Thanks, Robert

[jake-ruyi]

We actually brought everything back up literally yesterday. We're still doing some tests to verify everything is working (email notifications might not be), but it should be good. This took far longer to resolve than we expected. But, thankfully, there shouldn't be another disruption like this for at least a few months.

[jake-ruyi]

I may have spoke too soon. You might need to wait for the SDK update scheduled for Feb. 22.

TLDR; you can try it and see if it works. If it doesn't, it will with the client we release Feb 22nd.

There aren't significant changes to the C++ API you use, so it shouldn't impact your integration. What has changed is the registration/login portion of our main UI, now requiring a cellphone # as "highly recommended"/required by Chinese "real-name" mandate.

Normally, when we roll out an update there's both "old" and "new" server instances to cover multiple versions. In this case everything was brought up from nothing so there's no "old" servers, just the new ones.

I say you "might" need to wait because the "current" client (the one you've got) probably still works. The auth API is the same, we just added an additional "authentication identity" when a phone is used with the new client. But with Chinese New Year just past we didn't get a chance to test with the previous build.

A couple more things I'll mention:

• We're making sure it works with international numbers so registering won't be an issue for overseas developers like yourselves.
• You will have to re-create any user accounts your devs/QA/etc. might have been using; we didn't migrate the previous accounts.
• This all adheres to policy requirements because we'll soon submit the platform as part of government censorship approval so it has to be the "real thing". We're looking at moving the old SMS-less registration behind "developer mode" so it's less painful to create accounts for testing, etc.

[RobertKarp]

Hi Jake, We tried with the current SDK but without success. I haven't seen a new SDK drop yet, is that still planned to come soon? Thanks, Robert

[jake-ruyi]

Looks like the last blocker was resolved today, but not early enough to do a release. We'll make another QA pass tomorrow and hopefully do the release then. Sorry about the wait.

[jake-ruyi]

We're uploading binaries and pushing source to github at this very moment. It's a bit rough, but things should be back to mostly working.

[jake-ruyi]

Finally uploaded. Amongst other issues there's a bug with country codes when you logout and log back in. Have to manually change the "+86" to "+852" (or whatever) and remove the "852" prefix. Hopefully that makes sense:

[RobertKarp]

Thanks Jake! enjoy your evening :)