Cloud drive vanished from data exchange screen...
- Thread starter Charles Owens
- Start date
We are working on this issue. Unfortunately Google.Drive is out of order now. Due to strictness of Google security policy our web application has been banned and access has been revoked. We are in the middle of the process to get it back
Dear All
Google.Drive connection issue is resolved.
Unfortunately Google's security policy implies the least available access rights level to perform the Application functions. From now our Application has full control over the files it created itself. All the other files on Google.Drive are read-only.
To re-connect Google.Drive please proceed as usual. There may error screen arise. If so please navigate https://myaccount.google.com/permissions to perform full removal of 'J-Filed assistant' web application from your Google account and then re-connect.
Google.Drive connection issue is resolved.
Unfortunately Google's security policy implies the least available access rights level to perform the Application functions. From now our Application has full control over the files it created itself. All the other files on Google.Drive are read-only.
To re-connect Google.Drive please proceed as usual. There may error screen arise. If so please navigate https://myaccount.google.com/permissions to perform full removal of 'J-Filed assistant' web application from your Google account and then re-connect.
Hi Scott
there should be sliding refresh in action. You should never see errors related to access expiration.
Just in case you see 'expiration' error please make screenshot and post in this thread.
there should be sliding refresh in action. You should never see errors related to access expiration.
Just in case you see 'expiration' error please make screenshot and post in this thread.
I meant the device has a function to refresh this token automatically. As soon as the device face to token expiration error it does some token renew procedure that is why you should never see an error message on device. So the information about expiration in the web page is not quite important.
I see there may be another issue with a token on device. It may have been created before our application ban and therefore may not work.
It may be to worth perform an extra step. Dismount cloud drive to drop the old token and then mount again to get the new token.
I see there may be another issue with a token on device. It may have been created before our application ban and therefore may not work.
It may be to worth perform an extra step. Dismount cloud drive to drop the old token and then mount again to get the new token.