search

PlasmoHQ / docs

📘 Documentation site
https://docs.plasmo.com
12 stars 50 forks source link

Cannot update extension in Chrome #86

Open xeroxcsn opened 1 year ago

xeroxcsn commented 1 year ago

Hi, I found that the extensions, which are uploaded onto TestBed, cannot be update in Chrome today. They works well before and I just want to report the bug.

Fyi, the extensions on TestBed still can be published to Chrome Web Store by Itero and works fine.

So when I uploaded the new version of the extension onto TestBed, the displaying version on Itero Dashboard has been upgraded, but when I click on Update in the extension page, the extension did not update. I have tried to remove the extension and re-install it by the Install Page, but the one installed is still the previous version.

I think Plasmo is a really brilliant framework, thank you for the work!!

xeroxcsn commented 1 year ago

@louisgv do you have any idea on it?

louisgv commented 1 year ago

@xeroxcsn Thanks for flagging - can you check if the ID of the extensions match up?

xeroxcsn commented 1 year ago

@louisgv Thanks for the reply.

The extensions IDs are matched

And fyi, last time I can successfully update the extension was 2 weeks ago. 4 days ago, I just uploaded the extension as always, but this time the extension cannot be updated.

xeroxcsn commented 1 year ago

@louisgv I have just found that there is an error return from the sign api. I forgot to mention that I have integrated the upload process into CI. Do you have any idea on it?

The CI process is working fine on 26/10, and got 504 error start from 3/11

yixiangfeng commented 1 year ago

i have same issues. my steps:

  1. POST https://itero.plasmo.com/api/submit/upload (status 200)
  2. upload the zip file using PUT to step1 response url(like https://storage.googleapis.com/xxx/zip_files/xxxx?GoogleAccessId=xx&Expires=xxx&Signature=xxx). (status code 200)
  3. POST https://itero.plasmo.com/api/submit/sign (status code 504Gateway Timeout) response body 
    
An error occurred with your deployment

FUNCTION_INVOCATION_TIMEOUT