You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using clasp to push a file with Drive API should update normally and not affect the status of the Drive API.
Actual Behavior
If a project is using Drive API, clasp push shows the following message:
If you push and overwrite, the Drive API will switch to off here:
This will produce Drive errors in the Google Script:
However, the Drive API will remain enabled and untouched on the Google Cloud Platform API Dashboard.
The fix is simple in that after you push using clasp, you just need to turn back the Drive API. This isn't a huge issue, but thought I would bring attention to it. Took me a bit to figure out what was happening so I hope this will help someone else!
This is working an expected. The appsscript.json file defines which advanced services have been toggled on. If you pull a project before toggling it on in the UI, then toggle it on in the UI, then push the original file back you will have reverted that change.
On Thu, Feb 21, 2019 at 4:24 PM Eric Koleda ***@***.***> wrote:
This is working an expected. The appsscript.json file defines which
advanced services have been toggled on. If you pull a project before
toggling it on in the UI, then toggle it on in the UI, then push the
original file back you will have reverted that change.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#553 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Aawp81fVFBx0TlvaEbqZ8uxgGIlzQ-C8ks5vPro8gaJpZM4bHWD7>
.
Expected Behavior
Using clasp to push a file with Drive API should update normally and not affect the status of the Drive API.
Actual Behavior
If a project is using Drive API, clasp push shows the following message:
If you push and overwrite, the Drive API will switch to off here:
This will produce Drive errors in the Google Script:
However, the Drive API will remain enabled and untouched on the Google Cloud Platform API Dashboard.
The fix is simple in that after you push using clasp, you just need to turn back the Drive API. This isn't a huge issue, but thought I would bring attention to it. Took me a bit to figure out what was happening so I hope this will help someone else!
Perhaps this may be related to issue #513.
Steps to Reproduce the Problem
Specifications
node -v
): v10.13.0clasp -v
): 2.0.1The text was updated successfully, but these errors were encountered: