I assume 500 plus users of a group doesn't equate to active participants. Common sense would also presume it would take a considerable length of time to have hundreds of people install, test and feedback on any individual release.
New apple product, beta test by 500 users? Easy. Smaller companies - I just can't see it.
But hey, that's just a perspective/opinion.
I have no idea on the actual internals.
I would seriously recommend that individual users are utilised with these kids of situations, beta testers or not.
I hope this feedback is received in the manner it's intended. This isn't the only thread where it appears that people have had some frustrating issues, which (publically) appear to be left hanging.
There is a large beta forum... People only report what they find. Last beta for 2.3.9.x I found and reported 3 bugs, a few others chimed in and they were fixed.People won't report anything if they don't see an issue, but you have to sign up for the beta so they're actually active.
It seems the couple of issue lately are new. A couple of crisis fixes have been pu t out, the rest while annoying have been fixed already in development for 2.4.0.x. We're anxiously waiting for the beta. Not just because of bug fixes, but because of features...
Note: The 1st rule of beta club is "Don't talk about what's in beta club"
Someone will likely walk be into a basement shower soon as not to make a huge mess...
Are people still experiencing problems with this? I may or may not be. Some cloud-related things appear to be working ok, but others not.
The most pressing thing is that cloud endpoints created in one of my apps (using getFullApiServerUrl()) are not working, despite the local endpoints working. Produces the dreaded "No response from hub" error.
I had one occasion since .181 where I lost access to my cloud dashboards. A reboot of the hub fixed it. It's been fine since.
Kind of waiting to see if it happens again. The issue was very intermittent for me to begin with so I'm not sure if it was just a fluke or if the issue still exists on some level.
The number of incidents went significantly down since the latest update, but is too early to call the issue resolved, however, we are monitoring closely.
Both of your hubs are connected to the cloud at this moment.
Could this known cloud access issue possibly explain why one cloud endpoint created by one of my apps is producing "no response from hub" while other cloud endpoints created by others of my apps are working? I can find no other explanation on my end. Confused.
Just in case this helps everyone else my issue is related to the number of devices that I have on my hub ~600. Apparently oauth fails with "too many" devices. It is not clear what this upper limit is. I am not sharing all of the devices through maker so this relates to the devices created on the hub.
Support did follow-up with me, had me try a couple of things, and then indicated that they have seen something like this before related to the number of devices. They indicated that they would need to setup a hub with a lot of dummy devices to diagnose the situation. I had an eery feeling that this was going to lead to crickets - and it did.
So I didn't wait and went ahead and started moving all of the devices I share with Sharptools to another hub through hub mesh and sharing them that way. This is working. It is a little annoying to have to do this but at least I am up and running.
So just by having 600 devices on a single hub all OAuth was failing? Or was it specific to Sharp Tools only because it is asking for a list of devices (which obviously it has to do)?
Not related to Sharptools. I setup a test case on IFTTT wit one device shared and it did the same thing.
The response I got from support was "I'll have to create a special test case with tons of devices and try to pinpoint the issue. It has to do with the number of devices."
Please give it a try now. Our engineers have made changes to the oAth server that should help with time-out issues. Let us know if you continue to have any more problems.
