search

boukestam / inbox-in-gmail

Web extension that adds features of Google Inbox to Gmail
MIT License
123 stars 21 forks source link

Extension removed from chrome store #69

Open boukestam opened 5 years ago

boukestam commented 5 years ago

Hi guys,

Today I received this email: remove email

The extension is removed from the store until we make "some changes". It is very unclear as to what we need to change, so I've already replied to get some more information. I would like your help to figure out some things to change so I can reapply. What do you think needs to be changed?

@abasiri @g60madman @russelldc

espionagesoftware commented 5 years ago

I noticed in the "new" rejection email it adds this:

"Please ensure your item is not copying icons/screenshots from popular items in the store"

Note the word "popular" . Not sure what it is copying though. Other than Google's own icons.

russelldc commented 5 years ago

@espionagesoftware Every published screenshot up until then had been of either @boukestam's, @g60madman's or my own inbox. And as far as I know, Bouke hadn't copied the first icon from another extension. It could be argued it's a recolored Gmail icon, but that wouldn't explain why they rejected the re-submission that had the new original icon (unless it's because @boukestam didn't change the icons in the code). There are also several popular extensions that directly use the actual red Gmail logo in them.

boukestam commented 5 years ago

Ok guys, this will be my last try. The extension was rejected again yesterday, without any clear explanation. I'm really surprised by the lack of communication from Google, there is no clear indication of what exactly is the problem. If this doesn't work I will give up, since it's giving me a lot of stress. What are your suggestions for all of the following items:

russelldc commented 5 years ago

@boukestam Could you please answer my previous questions? It'd really help decide how to proceed.

What exactly did you submit yesterday?

Here's those previous questions I'd asked, above in this issue thread:

What did you submit as the extension's promotional images? (edit/note: the small tile, large tile, marquee images you mentioned in this recent comment)

What did you submit as the Short description?

When you submitted, did you change the extension's icon in the icons/ folder before packaging for the Chrome Web Store? If not, can you either commit those or upload them here? The master branch still has the old blue envelope icon .pngs in that folder. Also, could you add the screenshot of the Options page to the Chrome Web Store submission? That's in the README now.

I'll go make a 640x400 version of the Options page/popup. When you uploaded the screenshots, did you downscale from 2560x1600 to 1280x800?

If this last try still doesn't work, I could try uploading the extension from my account, if you wouldn't mind that. But man, it would really suck for all of previous users to be stuck and confused, on the old version forever.

I wish Google had better developer support :/

russelldc commented 5 years ago

For this last submission attempt, it might be worth it to create these kinds of descriptive screenshots, that Checker Plus for Gmail is using:

image

But I don't want to add any more stress on you, Bouke, you sound a bit busy. I'll try working on some like this tonight. When you get a chance, please answer the questions I'd posted above.

Ajedi32 commented 5 years ago

It's really frustrating that you keep getting generic rejection messages with no specific details about what we actually need to change to pass review. The fact that we all have to sit here and guess why the extension was rejected is pretty ridiculous.

No idea if this will work or not, but have you tried contacting support yet? https://support.google.com/chrome_webstore/contact/developer_support Maybe we can draft a message politely asking for specific details about exactly what needs to be changed to pass review? Google is notoriously bad at customer support, but it's worth a shot.

jcgoble3 commented 5 years ago

I really hope you don't give up on this. At the very least, please continue to to publish it in the Firefox add-on store and support it there. I use Firefox and cannot manage my email without bundling.

Muffo commented 5 years ago

@russelldc maybe you could try to submit from your account and see what happens? I wonder if @boukestam has been kind of black listed after they blocked the extension.

Also, the screenshots can be updated after the extension has been published. To narrow down the problem with Google you could submit it without any image and see what happens.

boukestam commented 5 years ago

I'm ok with others posting the extension, as long as there is a link and credit to this repository. So maybe that is a good thing to try.

russelldc commented 5 years ago

Sorry for the delay on making those new screenshots, I got really busy with work (had to travel for work over the weekend, too :/).

I'll try to get it done after work today, and if Bouke isn't around at the time, I'll submit from my account, and credit this repo.

@boukestam What'd you submit as the promotional images in the past?

pdarmas commented 5 years ago

Don't give up on this, a lot of people are really happy with this extension and your fantastic job . Pitty that the Chrome Web store team is not very communicative, but I have some spare time in my hands, if necessary.

joeytroy commented 5 years ago

Been a while since I chimed in, one thing I noticed maybe a problem is this. Regardless of bundle or no bundle it doesn't seem to work

image

russelldc commented 5 years ago

@g60madman What are you seeing in your inbox? It worked for myself and others. Did you follow the instructions in the readme/description?

If you disable it, you need to refresh to see the change. But as far as I can tell, if it's off and you toggle it Enabled, you don't even need to refresh, you should see the results right away.

joeytroy commented 5 years ago

@russelldc it's working now

russelldc commented 5 years ago

I saw this advice on a Google forum:

1. There is a Chrome Web Store Support form here "https://support.google.com/chrome_webstore/contact/developer_support/?hl=en", describe your situation there. 
2. Reply to the email that was sent to you with a request for explanation (you can recycle what you wrote from the form).
3. If you do not receive a response within a week, submit another form. 
4. When they do reply to you, make sure you find out the exact reason your extension was taken down.
5. The reply may tell you which file from your extension they have a problem with specifically. Try to fix this file and resubmit your extension as an update.

I also saw a blog post from someone who replied back to the rejection, and a few hours later received this:

Thank you for reaching out to us.
Upon a subsequent review, we’ve reinstated your item and it is now available in the Chrome Web Store.
Muffo commented 5 years ago

The screenshot is horrible, there is no icon and the description is missing... ...but at least the extension is available on the Chrome Web Store for those that can't take it from the repo.

I'll take it down as soon as the official version is uploaded. In the meantime I'll upload a new package from time to time when the repo is updated.

russelldc commented 5 years ago

Sorry for disappearing for 2 weeks (though it seems like most others did too!). I've had a lot of projects starting/ending at work. I'm hoping I can get back on this sometime this week. Thanks @Muffo for getting something up 👍I'd really like to eventually get Bouke's original listing up so those users don't get lost and confused. Based on a few articles I read, it seems like it would be worth continuing to email Chrome Store dev support or fill out that form linked above, although only @boukestam can do that.

jcgoble3 commented 5 years ago

Trying to get some more attention here for #81. The Firefox add-on store listing has been completely ignored since this happened, and the latest version there predates bundling, which is absolutely critical for me. I have therefore been forced to repeatedly load the extension manually through the debugging interface every time I launch Firefox, which is now up to a dozen times a day since I now carry a portable version of Firefox for use on college computers.

What needs to be done to publish an update to the Firefox add-on store? Or must I create my own account and publish it myself as a fork?

jcgoble3 commented 5 years ago

Comment above has been resolved. Please ignore. Thanks!

Henboy10 commented 5 years ago

Hey! I don't know if you guys know, but the Chrome Web Store listing link is dead. Just thought I'd let you know :)

Muffo commented 5 years ago

Yes, I received an email yesterday saying that the extension had been taken down. Basically for the same reason the original submission was removed.

arxae commented 5 years ago

Isn't it an option to supply supply the CRX file for manual install (until the store debacle is resolved)

Muffo commented 5 years ago

Yes, it's possible to create releases in Github and attach the CRX file there. This has to be done by the owner of the repo, though.

richardfrost commented 5 years ago

@Muffo The listing that you created was version 0.5.0, but the latest "official" release is 0.4.7. Did you just use master, or did you make any other changes? Apparently Chrome removed the extension from my browser, and I'm hoping to get it back.

Thanks to all who have been helping out - this is a great extension!

Muffo commented 5 years ago

Yes, I had simply used master.

richardfrost commented 5 years ago

Thanks for the response. One last question @Muffo, when you mirrored the extension on the Chrome web store, did you set the visibility as "Public" or "Unlisted"? I'm wondering if unlisted might give it more protection from being removed until this mess gets sorted out.

Muffo commented 5 years ago

Good question! It was posted a Public, but I am not sure if hiding it would help. I wonder if Google uses some sort of automated scan tools to detect violations in their guidelines. At this stage, I am still not sure what the problem is.

russelldc commented 5 years ago

I think Unlisted would actually work -- I was planning on suggesting it for now, until we sort this out with Google, but forgot. I'm not sure you'd be able to make the denied one into Unlisted one, though.

Now that you've gotten refused, can you try responding to them, @Muffo? I think Bouke was too busy to follow up.

As I'd posted in an earlier comment here, I saw this advice on a Google forum:

1. There is a Chrome Web Store Support form here "https://support.google.com/chrome_webstore/contact/developer_support/?hl=en", describe your situation there. 
2. Reply to the email that was sent to you with a request for explanation (you can recycle what you wrote from the form).
3. If you do not receive a response within a week, submit another form. 
4. When they do reply to you, make sure you find out the exact reason your extension was taken down.
5. The reply may tell you which file from your extension they have a problem with specifically. Try to fix this file and resubmit your extension as an update.
russelldc commented 5 years ago

@arxae @richardfrost I published a new release of v0.5.1, including a crx file

https://github.com/boukestam/inbox-in-gmail/releases

richardfrost commented 5 years ago

@russelldc Thank you so much for the creating the new release!

LLI-inc commented 5 years ago

Hi, I'm a user and I just read through this whole thread and it makes me sick what they're doing to you guys. It's so infuriating! I LOVE this extension and in fact, can't live without it!

I had looked for it in the chrome store several times over the last few months to see if there was an update and was so disappointed and frustrated when I couldn't find it. The only way I ended up here is because the icon that the original one put on my web browser, linked to here. So I'm really glad to see you are still trying.

So, you haven't been able to get any reply from that Google developers' contact page?

russelldc commented 5 years ago

@LLI-inc I'm not sure if any of the others have had time to continue reaching out to Google's extension team. @Muffo @boukestam ?

I would have done it myself by now, but I've never uploaded it to the Chrome Web Store because I thought it might complicate things further, considering they have rules for not copying another extension on the store. I don't think I could contact them on another developer's behalf.

In related news, I got this email from Google recently:

We recently announced changes as part of Project Strobe that expand our efforts to ensure all Chrome extensions are trustworthy by default. This announcement includes the requirement that extensions request the narrowest permissions needed to implement their features, and that extensions that handle personal or sensitive user data post a privacy policy and handle user data securely.

The new policy, found in our updated Developer Program Policies, reads as follows:

Use of Permissions

  • Request access to the narrowest permissions necessary to implement your Product’s features or services. If more than one permission could be used to implement a feature, you must request those with the least access to data or functionality.
  • Don't attempt to "future proof" your Product by requesting a permission that might benefit services or features that have not yet been implemented.

Posting a Privacy Policy & Secure Transmission

  • If your Product handles personal or sensitive user data (including personally identifiable information, financial and payment information, health information, authentication information, website content and resources, form data, web browsing activity, user-provided content and personal communications), then your Product must:
    • Post a privacy policy, and
    • Handle the user data securely, including transmitting it via modern cryptography

Your extensions must be compliant with this policy by October 15th, 2019. You can learn more about these changes and how they may apply to you in our User Data FAQ.

If you have any questions, please reply to this email. You can also sign up for open office hours for Chrome Extensions.

The soonest available open office hours is August 29th as of today, and it looks like they have them every Tuesday and Thursday from 4-6PM UTC.

Our extension doesn't collect or store personal or sensitive user data, as far as I can tell from how it's defined in the User Data FAQ. And we have a privacy policy of sorts explaining this in the description.

4. My Product DOES NOT handle sensitive or personal data. What do I need to do? You have no special or new obligations under the User Data Policy. Please state in your privacy policy that you are not handling user data.

joeytroy commented 5 years ago

This sounds a like a good time to resubmit. Honestly I think if we merged all the code into back into https://github.com/inbox-in-gmail I think any of us could push to the Google store who is a dev? Just thought.

russelldc commented 5 years ago

@g60madman Doesn't really matter what GitHub repo it's on, you just upload the packaged binary (the .crx file).

Like I mentioned in my last comment, I hadn't yet uploaded it myself to the Chrome Web Store because I thought it might complicate things further, considering they have rules for not copying another extension on the store. I hoped (and preferred) that we could revive the original listing of the extension, so all those users aren't stuck on that old version. If Bouke is a no-show though, I might as well go ahead now.

joeytroy commented 5 years ago

I for one am fine if you want to post. I still think we should leave https://github.com/inbox-in-gmail the master repository as we have multiple admins associated with the repo so in the event something happens to a member the repo can continue on. Just my two cents.

joeytroy commented 5 years ago

@russelldc @boukestam I know it's been a while, have we decided to try and release the extension again? If not I have some free time and can post it along with creating a website and also YouTube video as well. Let me know your thoughts. Again I say we leave https://github.com/inbox-in-gmail as the main repo.

Somehow these guys still have their extension accepted and I think it has to do with the YouTube video and also website. Let me know and I will start work on it.

https://chrome.google.com/webstore/detail/inbox-theme-for-gmail/albppgldjlaflgenhggocpigdgdmgpee

russelldc commented 5 years ago

@g60madman I'll get it up there tonight, thanks for reminding me. I merged latest into the inbox-in-gmail/inbox-in-gmail fork and updated the home page to point there instead.

I'm a little unconvinced that the video is what made the difference, but who knows? I figured they would judge based on the content provided, not on an external site. I think it's just as likely it was just random. That other extension was uploaded before this one, and was never updated since January, so it wouldn't have been re-reviewed.

joeytroy commented 5 years ago

Website is up. I also renamed the team site and repo

https://www.teaminbox.dev/ - Our website

https://github.com/team-inbox/ - Our team

https://github.com/team-inbox/inbox-reborn - Our code. I also activated issues as well so we can track them from the main repo now.

I am hoping to get the video done this week and published right now the website has the original Google Inbox video but I will get it updated to the video to show off the plugin. Once the video is published I will push the code to Google.

russelldc commented 5 years ago

👍Although, I'd recommend instead of a separate Wordpress instance, it could just be hosted directly on GitHub. See here for details, if you're not familiar: https://pages.github.com

We can have the teaminbox.dev domain point to it, as well, so it's not just team-inbox.github.io

Edit: It's available at https://team-inbox.github.io/inbox-reborn (obviously placeholder content) If you point the teaminbox.dev domain there, it should work straight away, I have the required CNAME file in place. When anyone commits changes to the /docs folder of the repo, it automatically pushes a release to our GitHub Page.

drazil100 commented 5 years ago

Is there any news on the progress of getting this back in the web store? Is the project still alive? The Inbox Theme for Gmail extension kinda broken and when I submitted an issue on that project's github I was made aware that this existed. Unlike the other extension which was just a theme this actually brings back functionality so I would be very much interested in using this extension instead.

arxae commented 5 years ago

Doesn't look like there is much activity at all. @boukestam seems to be absent from GH since september and the most recent fork (https://github.com/team-inbox/inbox-reborn) hasn't seen any activity for 2 months either.

drazil100 commented 5 years ago

I noticed that as well. It would be really nice if I didn't have to manually install this on every machine I check email on. Hopefully someone reads this and revives the effort to get this on the web store :P

richardfrost commented 5 years ago

It seemed like @russelldc was going to take over, but maybe he got busy?

I'd be willing to publish it if none of the contributors want to. No guarantee it won't get taken down again, which is probably why there has been delay and hesitation.

joeytroy commented 5 years ago

I spun up a website for Team Inbox team and was planning on releasing a YouTube video showing off the application and then posting the extension. Just haven't gotten there yet as I have been really busy as of late. Here is the site, if some one wants to create video showing off the differences that would fantastic and I then I can post it up https://www.teaminbox.dev/

gwilty-pixel commented 4 years ago

Hey, I use the extension on chrome on other devices. Today I can not use the extension on my new computer, due to the disappearance of the extension of the chrome webstore. Is the project abandoning? is it possible to take advantage of the extension by another means?

thanks for your reply

LLI-inc commented 4 years ago

@gwilty-pixel - Go to this page: https://github.com/boukestam/inbox-in-gmail/releases/tag/0.5.2 and download the inbox-in-gmail.crx file.

Then, open the Extensions page on your Chrome / Chromium browser and drag and drop this file onto that page. It will install automatically and you'll be good to go!

gwilty-pixel commented 4 years ago

thanks for the reply i did it, but i have the message : This extension is not listed on the Chrome Web Store and may have been added without your knowledge.

Annotation 2019-12-10 200715

i can't activate it and i'm in developer mode

gwilty-pixel commented 4 years ago

here is the official chrome webstore help [answers] :

Use disabled extensions If you need to use a disabled extension, you can contact the extension’s developer and ask them to upload their extension to the Chrome Web Store. This will allow you, and other people who use Chrome, to install that extension from the Chrome Web Store, or if you already have it installed, to manually re-enable it from your list of extensions.

richardfrost commented 4 years ago

You might try loading an unpacked extension. Just download the Source code.zip file from the Releases page, extract it to a folder and follow the steps linked above for loading an unpacked extension. This will cause a prompt every time you start Chrome that you'll have to acknowledge, but its not TOO bad. Hopefully we can get a real store release again soon.

gwilty-pixel commented 4 years ago

here to say thanks you! hope will back soon in store!

👍