With GWS v2.0.0 or 2.0.1, generating certificate both author or distributor invariably ends with a “timeout” message after signing the samsung account … I tried many times but always with the same result.
I just saw someone with Tizen Studio has the same issue.
It looks like this is a store issue. I’ve seen it happen before. Usually it works after a couple days. However be sure you are not using Internet Explorer as the default browser and I’m not sure on FireFox either.
If this drags on for more than a couple days let me know and I’ll escalate the issue.
The certificate server has been returning 408 errors since at least Tuesday morning (in the UK), so at least 54 hours. I’ve tried going through both Galaxy Watch Studio and Tizen Studio to see if there’s any difference but no joy.
I was going to start my first proper project on Tizen this week as well!
Worked for some days. Now Author Certificate no longer accepted (no changes made!) - Generating a new one: TIMEOUT … it ist really unbelievable: Version 2.0.1 is unusable since October due to the AOD-Bug and 2.0.0 ist now also obviously unusable…
Apparently the fix only fixed the Distributor Certificates and not the Author Certificates.
You do not need to generate a new Author’s Certificate (and never should) did you back up the old one as instructed? If so you can create a new Distributor Certificate. The Author Certificate is only needed to build your watch face not run on device.
I reported this and since they know what the issue was hopefully they can fix it early Monday.
I wonder why it worked for at least one day!? Yes I do have a backup of the certificate.
Now it says Author Certificate not match [-11]. Therefore I wanted to generate a new one. With the timeout result. Should I simply copy back the old one and wait until it works again (if ever)?
I didn’t realize it was both Author and Distributor Certificates so only reported the Distributor certificate. Hope fully they will fix this quickly. I escalated this over the weekend and hope they fix it soon.