Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Foxify gives a misleading response after a conversion attempt fails #109

Open
HubJ opened this issue Jan 7, 2018 · 3 comments
Open

Foxify gives a misleading response after a conversion attempt fails #109

HubJ opened this issue Jan 7, 2018 · 3 comments

Comments

@HubJ
Copy link

HubJ commented Jan 7, 2018

This problem was observed in when trying to install a Foxified version of LastPass from Chrome Store in FF 52.5.3 ESR on Windows 7 SP1.

As reported in another Issue, the attempt to convert the Chrome extension failed with the message that "AMO validation failed." However, unless I opened the Foxify menu, cleared memory, and restarted FF, I could not begin the process again, although I was given the option to "retry."

By "begin the process again," I mean going back to the Chrome store, to the LastPass page, and clicking the "Install in Firefox" button, If I tried to do this, I got the message, "You have previously already downloaded this extension." However, even if it had been, in fact, downloaded, it is a download of a Foxified plugin that didn't work. I found two such dead extensions in my Firefox Profile folder.

Keep in mind that a novice user, or a less determined one, would have no idea what do do at this screen.

I think Foxified should keep track of whether its install attempts fail, and display a message similar to this in such situations, "Your previous attempt to convert this extension was unsuccessful. Would you like to remove it from your Firefox Profile folder, and then return to the Chrome store to try the conversion again?"

@lucasho2312
Copy link

where exactly in profile folder did you find them?

@Noitidart
Copy link
Owner

This is super detailed, thanks for this. Let's try to fix this up. I'm working on reviving the addon right now.

@HubJ
Copy link
Author

HubJ commented May 27, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants