People can still download GWS 2.0.1 despite the many bugs
Hi GJL
The biggest bug is it doesn’t save the AOD and that is an big issue.
Since it took over a year to get an update to 2.0 I have doubts there will be any future updates.
But it does fix many bugs . See the Release Notes
Ron
Samsung Developer Relations
where can i download version 2.0?
To clarify Redacted
just below where it says download are the S Previous Versions.
Ron
Samsung Developer Relations
Thanks for the explanation, I really missed this. 2.0 installed. but still I get the message 65% again. so same message.
The 65 percent and time out error is generally failure to accept the RSA Encryption key
Reboot your watch by holding down on the power button for about 15 minutes until it says rebooting
Restart your computer to be sure all caches are cleared
Check that developer options and debugging are enabled on watch (they should be but check)
Connection is made to Wifi it isn’t automatic but always on.
Change your watch face to a factory installed watch face
Launch GWS wait a full minute for it to be fully loaded
Select Run on Device and your device
Observe your Watch like a hawk and when the RSA Encryption pops up OK it
It should then load and run on the device.
If it still fails then you need to create a new Distributor Certificate.
If that fails you probably will get a different error message or it just hangs if that is it let me know.
Ron
Samsung Developer Relations
Delete the TW4.tpk of the WF and rebuild it and the error should be done
Hello from the Netherlands
Did all steps again, watch hard reset, computer started up and stuck at 65% when a new login was made. reset again. 65% hang. then also loaded the distubute (I don’t need it) but I have the idea that GWS works again with this. After biting my nails for 5 nights. And now I was able to upload a few dials to my watch again. Pffffff
Ron thanks for your patience.
You didn’t happen to update your system to Windows 11 did you? Any watch version upgrade or computer system upgrade requires a new Distributor Certificate.
There are two certificates, Author is the one that tells Samsung who you are when you upload to the store so they can contact you if there are any bugs.
The other is the Distributor Certificate and that tells the watch that it is safe to allow installation for debugging. Distributor certificate is only for specific computer and specific watches.
Ron
Samsung Developer Relations
Yes Ron I had upgraded my computer to win 11 so now it is clear that you have to create a new Distributor Certificate.
But I’m glad we got out, it was a few evenings of work. but it works again thanks…
Some mistakes:
AOD does not survive even for new projects.
Clock screens do not show sensor permissions after publication. They must be installed manually.
Buyers complain. I checked it myself.
When testing GWS, permissions appear automatically. Disappears when publishing.
Unless you are on Mac OS the problems created are worse than the bugs that were fixed, go back to GWS2.0.0 (previous versions downloads) If you do use 2.0.1 back up all your projects prior to opening them or it will corrupt all the AOD’s
AOD does not survive even for new projects.
If you open the project in the 2.0.0 version it will show the AOD you created. It just fails to open them in 2.0.1 for Simple AODs you can save the AOD as a custom complication but it is much more problem than just reverting back to the older version.
Clock screens do not show sensor permissions after publication. They must be installed manually.
Buyers complain. I checked it myself.
When testing GWS, permissions appear automatically. Disappears when publishing.
I think this is a requirement by new GDPR regulations, I haven’t done it in Tizen but I noticed it started happening in Wear OS after an update.
I just got a Windows 11 and will give this a try with GWS 2.0.0 to see if it forces permissions. GWS 2.0.1 was a royal pain and I through in the towel and went back to 2.0.0 .
Ron
Samsung Developer Relations
Good afternoon. I’m using a Windows computer. When you create a GWS clock and test it on the clock, everything works as it should. Notifications pop up and require access to sensors. But as soon as the program loads in the store, it starts having problems. Notifications do not appear.
And. Thanks for the advice. It’s a pity I noticed it late. Buyers noticed. Now I just have to redo a couple hundred programs. 
Interesanti ko dara testētāji. Ko neko neteica? 
As far as I know nothing in GWS requires sensors so do not understanding why they would pop up unless you have an app ID for an action item.
Just to be sure we are talking about GWS and Tizen OS not WFS and Wear OS
Ron
I’m talking about GWS and Tizen OS. Downloading the store clock screen. You will understand better in the picture.
Thanks that picture did help. It does look like the GWS has a bug in it and not setting permissions correctly but I don’t know if it is or GDPR rules.
Some questions so I can know where to report it.
Is it with everything that uses Sensors or just Health content?
Is this with both Tizen 4.x and Tizen 5.5 or just one of them?
Simple solution seems to be just roll back to GWS 2.0.0. the project files created in 2.0.1 open fine in 2.0.0 and your AOD is saved.
And thanks for taking the time to show the images It really helped me understand.
Ron
Samsung Developer Relations
I can only test Tizen 4.x. Tizen 5.0 I don’t have the right equipment.
I’m not sure, but it seems that there could only be a problem with health sensors. At least they are complained about by users.
Programs from GWS 2.0.0 display a notification and require sensor permissions.
Tizen 5.0 versions cannot be created with GWS 2.0.0.
Also, some users have complained that the programs cannot be purchased after the end of the trial period. But it was already GWS 2.0.0 and earlier.
I hope this helps somehow. Have a nice day.
Programs from GWS 2.0.0 display a notification and require sensor permissions.
Tizen 5.0 versions cannot be created with GWS 2.0.0.
Tizen OS is backwards compatible and Apps created for Tizen 4 run just the same on Tizen 5. Also there are no Tizen 5.x features supported by GWS 2.0.1 that are not in GWS 2.0.0 Tizen 4 build so unless you are affected by one if the minor bugs there is no reason to use GWS 2.0.1.
Also, some users have complained that the programs cannot be purchased after the end of the trial period. But it was already GWS 2.0.0 and earlier.
It seems that there has always been issues with GWD and GWS In-App-Purchase trial periods I think they are from store changes,
Ron
Samsung Developer Relations