I've been struggling to get my update to go through. I incremented my version in the manifest and updated a lot of code, I upload the new package successfully and submit, but I never see the manifest version update in the chrome web store and there are no errors. The draft of the package always shows the same version as well (0.0.0.1 as I have never had a successful update). When I submit the status goes to pending and then public.
My only guess is that something is wrong with my account. This update includes moving from manifest v2 to v3 as well although I feel like I'd get an error if something was wrong there.
I've tried to resubmit this multiple times over the past 3 weeks and always the same lack of update.
There were a few .pem files in a random node module. I hadn't realize I should just remove node_modules from the zipped up package, but for some reason it only errored out and warned me about including .pem files sometimes. Most of the time updating the package seemed to work fine and didn't error. Very strange. Regardless it is fine now!
Related
Not sure what details I should be providing to be completely honest, other than I googled and searched for this solution and I deleted everything and retried and didnt work out, I downloaded all the files needed, I added application settings and it added an error for me telling me that I need to install or update Microsoft.WindowsDesktop.App, version 3.1.0, which I have installed and already existed anyway
I tried going to application event logs on Azure portal, there was 3 errors first this one which some people suggested going to web.config and changing it to Module not v2, and I dont see any web.config file in my mvc project
2nd error which I already talked about but its just not working, so I assume somehow its not seeing it??
3rd error Also this I am not quite sure what to do with it.
Lastly, as I said I am not sure what information I should provide, I dont have much time and I was asked to publish it on azure there was no problems and seemed easy but errors popped up and nothing on the internet fixed my issues, you can comment and I will add any required data to fix this.
Thanks in advance
I installed each and every package in the dotnet folder to make sure everything is right and everytime it recognized there is a file already and asked me if I want to repair I said yes but that didnt help
I checked my .json file if it had any errors like some people suggested
checked if Azure portal specified that I am using ASP.NET 3.1core which it did
~~I used search for "stdoutLogFile" to check if I can find it anywhere on my solution since I cant find my web.config but I there was no result~~
I found out that I can add the web.config and make changes to it, and I did so but there was no result for it, still same error (yes I change the publish profile and republish to make sure it took the changes)
[enter image description here][1]
[1]: https://i.stack.imgur.com/rgiVi.png I got these errors when I opened the profile.arm.json folder under the server dependency folder
My goal is to make sure I have a stable process for handling extension updates. I'm about to release a new extension and have noticed that the background service worker goes stale. Here are the details:
My method of testing this lifecycle is by generating a new build artifact and drag-n-dropping it into the page chrome://extensions. I hope this is the way to test this lifecycle. But if not, I would be happy to hear the alternative.
Once I drag and drop, I open the background console to check for the correct version, but seems it lags behind. The only way to remedy this issue is by removing the extension completely and loading it back, this gives me the impression a regular user would experience the same issue.
The screenshot below describes the situation:
version 0.3.33 is currently installed
drag and drop new build version 0.3.34
after successful drag and drop, notice version is lagging with version 0.3.31
But the chrome.runtime.onInstall release accurately outputs the previous version
Furthermore, I took a look at the unpacked extension directory and the compiled code is accurate with the expected version
What I've done so far to troubleshoot, was to remove the extension completely. It does successfully update after a series of manifest.version updates, but then it goes stale. To be clear, all I do is update the version property of the manifest.json file and that seems to cause this issue
Any help would be greatly appreciated. In the meantime, I'll brush up on the architecture for service workers as it relates to chrome manifest v3. Thanks!
EDIT - Sunday, August 22 2021:
The latest development:
First of all, thanks woxxom for additional details to debug.
I've created an example project that demonstrates the problem with reproducible steps. Hopefully, this helps identify the problem but it does seem to point to a Chrome bug so I'll also report it on crbug.com
Github project: https://github.com/miguelespinoza/-v3-service-worker-update
Ultimately, what I've identified is that loading an iframe causes the service worker lifecycle to go "stale".
Looking at chrome://serviceworker-internals/?devtools, I've noticed that the extension includes two workers, that seems odd because I'd imagine only one should exist, the one in the background. This could mean nothing, but wanted to share that as well. one "Active worker" and one "Waiting worker"
Important Note: Service worker background events stop working. In my case, chrome.commands.onCommand or chrome.action.onClicked
No idea what happened... It was working and then it wasnt.
I am currently building a web app and decided to take some time off from the product side and build a landing page.
For some reason, I decided to build the landing page on a separate Github branch. So I checked out to a new branch, deleted everything, and started working on the landing page.
I soon realized this is a terrible idea and created a new repo to store my landing page.
I checked back into my master branch and spun my Node server up but for some reason now, everything is timing out. I opened Postman and tried hitting some of my endpoints but after like 3 minutes of loading, it tells me that it could not get any response and that there was an error connecting to localhost:3001/api/posts
In my terminal, all I see is this when I hit the route:
GET /api/posts - - ms - -
This has never happened to me before and I am completely clueless on WTH happened.
I tried deleting my local stuff and re-cloning the repo and installing my dependencies but to no avail...
Would love to know if someone has an idea on what's going on.
Check first is this isn't because of another process already listening on that port (but using resources which were deleted or not properly updated)
Closing applications or even rebooting can help you asserting if the issue is permanent or just linked to your current session.
The OP Syn points out in the comments the ~/.env file missing
.env files allow you to put your environment variables inside a file.
You just create a new file called .env in your project and slap your variables in there on different lines.
To read these values, there are a couple of options, but the easiest is to use the dotenv package from npm.
npm install dotenv --save
Note: it is generally not versioned, as it includes potentially sensitive date.
I know that when you publish a new version of your extension to the Chrome Store, you're supposed to increment the version in the manifest file. BUT what if I publish an update WITHOUT incrementing the version? What I would want to happen is that the old users that already have the extension don't get the update, but any new installers get the latest version. Is that what would happen?
The reason I want to take this approach is that the new version of my extension will request increased permissions, and I don't want the extension to auto-disable for all my old users where they are then asked if they want to enable it given the new permissions, and that's what happens when there's a permission level increase. I'm afraid that if that happens, my install counts will drop.
You can't upload a package with the same version number as the already published one, just tried myself and got this error:
An error occurred: Failed to process your item.
Invalid version number in manifest: 1.8.2. Please make sure the newly uploaded package has a larger version in file manifest.json than the published package: 1.8.2.
Writing an android application. It has no errors when I run it on an emulator. But when I tried to build it to an apk file to test on a device, I get the following error.
com.intellij.openapi.project.IndexNotReadyException: Please change caller according to com.intellij.openapi.project.IndexNotReadyException documentation
at com.intellij.util.indexing.FileBasedIndexImpl.handleDumbMode(FileBasedIndexImpl.java:853)
at com.intellij.util.indexing.FileBasedIndexImpl.ensureUpToDate(FileBasedIndexImpl.java:802)
at com.intellij.util.indexing.FileBasedIndexImpl.ensureUpToDate(FileBasedIndexImpl.java:786)
at com.intellij.psi.stubs.StubIndexImpl.processElements(StubIndexImpl.java:250)
at com.intellij.psi.stubs.StubIndexImpl.processElements(StubIndexImpl.java:238).......
I seen one similar case raised here which mentions to "Wait till indexing is complete."But I am not sure what I am doing to even interfere with any indexing.
Tried on different computers. Same problem. The only thing I did different before I got this error was to add a dependency at gradle(app) for a RingButton and added that RingButton class to the project to modify it to what I wanted.
As I said it is working fine in emulator.
Just to test if that is indeed the isse, I deleted the class and removed the dependency but the issue is not resolved.
I think this can be solved by creating a new project and moving the files into the new one. Maybe the index is corrupt. But before that can you clear the cache ? in android studio if your prepared to lose some local history then try this:
and then chose invalidate and restart:
I was using Dropbox to constantly backup my project every now and then. So I would click my project and send to Dropbox. I was also instantly clicking run to run the app on my emulator at the same time. During this period, when I mouse over my Dropbox icon, there is an indication that it is "Indexing".
Based on previous answer "Wait till indexing is complete", I can only assume this Dropbox indexing interfered somehow.
Not exactly elegant but I copied each and every file in this project into a New Project and everything is working fine now and able to install the apk file. I didn't change anything so I believe there is some form of corruption in the old project.