vscode-azureappservice icon indicating copy to clipboard operation
vscode-azureappservice copied to clipboard

I have upgraded my subscription to pay as you go and none of my apps work on azure site but run locally perfectly fine

Open YohanesDemissie opened this issue 6 years ago • 3 comments
trafficstars

Repro steps:

Action: appService.Deploy Error type: ReadOnlyDisabledSubscription Error Message: The subscription 'fdfacc9d-3986-4f1b-9433-cdf4c49713b9' is disabled and therefore marked as read only. You cannot perform any write actions on this subscription until it is re-enabled.

Version: 0.13.0 OS: darwin VS Code Version: 1.32.3

Call Stack
module.exports.Ps.a.pipeline (dist/extension.bundle.js:277:2546875)
s (dist/extension.bundle.js:277:112563)
s (dist/extension.bundle.js:165:26036)
dist/extension.bundle.js:165:27276
o (dist/extension.bundle.js:223:7054)
dist/extension.bundle.js:165:24957
$.module.exports.t.requestLibrarySink.t.headersOnly.t.streamedResponse.t.body.function.t.body.pipe.a [as _callback] (dist/extension.bundle.js:1:521656)
$.module.exports.$.init.t._callback.t.callback.t.callback (dist/extension.bundle.js:253:5461)
$.emit (events.js:182:13)
$.<anonymous> (dist/extension.bundle.js:253:18274)
$.emit (events.js:187:15)
IncomingMessage.<anonymous> (dist/extension.bundle.js:253:17116)
Object.onceWrapper (events.js:273:13)
IncomingMessage.emit (events.js:187:15)
endReadableNT (_stream_readable.js:1090:12)
process._tickCallback (internal/process/next_tick.js:63:19)

YohanesDemissie avatar Mar 28 '19 04:03 YohanesDemissie

I have the same issue, VSCode seems to be caching the "Free Trial" information and its disabled state, however the upgraded subscription (pay as you go) has the same ID.

interestdashing avatar Apr 06 '19 18:04 interestdashing

Workaround - uninstalling extension, restarting vscode, and then reinstalling extension then allowed deployments. It still showed the title of the subscription as "Free Trial" instead of the newly named upgraded subscription name however.

interestdashing avatar Apr 06 '19 18:04 interestdashing

@YohanesDemissie @interestdashing

Thanks for reporting this. I'll forward this to the azure-accounts repo since this seems to be an issue on their end. Thanks for the workaround too, sorry for the inconvenience!

nturinski avatar Apr 08 '19 18:04 nturinski