We have a Google Sheets add-on from the Google Workspace Marketplace. There is a hate review, we report that, but the marketplace did anything. So we are thinking of re-publishing the add-on. So my questions are:
If we un-publish the add-on and publish it again, will all the previous reviews be removed?
How could we keep the name of the add-on during the whole process of un-publishing and publishing?
Official documentation below:
Publish an add-on
Overview: Publish an app
Does not indicate whether to unpublish and publish the Add-on again would remove the review.
As instructed by another community member:
"... If you unpublish and republish the app you'll have the same name, installations and reviews ..."
Leaving the option of the Add-on removal to achieve the review deletion not viable.
An alternative to this would be to report the review as instructed here under 'Rating and review policies' based on 'Offensive content' as it states:
"... Reviews that violate the following policies will be removed ..."
AND
"... Google will remove content that contains obscene, profane, or offensive language or content. ..."
Another alternative was provided by the same community member to submit an issue report here so it can be reviewed internally by the Google Team.
Related
i have recently added a product to the task management section of the Google Workspace Marketplace which has been approved and if I search for it I can find it. But if I click on the task Management category I do not see it in that list. Is that list limited, if yes, how do you get to appear in that list?
Many Thanks
Colm
Added saas product to task management category but am not able to see it in that category.
It appears that the "Publish to the Web" feature for Sheets no longer allows downloading of a sheet by URL, unless the "Share" feature is set to share to "Anyone with the link".
Up until yesterday, 11/18/2020, this extra step of making sure the "Share" setting was in place was not necessary.
Can you please confirm if this is a bug or a new and expected change? Thanks! ^_^
This seems to be a bug:
If a spreadsheet is Published to the web, it won't be accessible in any of the file formats (.csv, .pdf, .ods, etc.) to users who don't have access to the spreadsheet itself: for these users, it will only be accessible as a Web page.
This is not intended behaviour, since files that have been published to the web should be accessible to anyone with the link, no matter the sharing settings the spreadsheet itself has.
Issue Tracker:
This behaviour has been reported in Issue Tracker several times: see this issue, this one and also the one you mentioned.
Specifically, the following issue seems to have been getting more traction, and it has already been reported internally by Google (see comment #3):
Private Sheet public CSV export requires authentication
Therefore, I'd suggest anyone affected by this issue to click the star on the top-left in order to be notified of updates and to help prioritizing this.
Workaround:
Share the spreadsheet itself with Anyone with the link as Viewer role.
I'm trying to add an account to my Xcode, but I keep receiving this error. The same account on another Xcode works perfectly. I have other accounts working just fine.
The error is (as stated on the title)
The role information in the response does not contain any known roles: (MEMBER)
Image with the error:
For anyone still having this issue:
For me the bug was caused because i had an expired developer program together with multiple other valid developer programs. (XCode Version 7.3.1)
The apple homepage doesn't allow you to leave a developer team, that is expired (state 07/2016).
You can still leave the team by disabling the CSS that hides the button from you, with any Browser homepage analysis tool.
Go to the expired team to "Membership"
For Chrome right-click -> Analyse
Following steps on the screenshot attached:
Search for "leave" within the html tree
Click the "li" element
search within the styles for "hide"
disable the "disable: none" css style
Now you can leave the team as usual.
Disabling the ng-hide style
The workaround to this problem is to add a new Admin account:
Create a new Apple ID (ex. support#yourcompany.com)
Invite this email address at https://developer.apple.com/account and click on People > Invite People > Invite as Admim
Add the new Apple ID to XCode > Preferences > Accounts
I'm also working with apple to resolve the bug you reported. But, at least I'm able to submit new builds of apps.
Am integrating branch.io to my iOS app which is being developed in Xamarin, without Forms.
Followed the steps mentioned in SDK integration.
Added the Branch Xamarin SDK as a NuGet package
branch_key added in Info.plist
Added URL scheme in Xamarin
Enabled Universal Links in branch.io portal
Added code for initialization and delegates for branch.io
Enabled Associated Domains in developer portal
Enabled Associated Domains in xamarin studio and added domains applinks:bnc.lt
Ensure that the correct build target is checked in the right sidebar.
Am not sure how to do that in xamarin. By default the Entitlements.plist file is specified in configuration.
Enabled Universal Links in branch dashboard
Specified bundle identifier and Apple App prefix properly.
Created a marketing link, and tapped the link from messages app.
Which routes to safari with a dummy page from bnc.lt, with option of 'Get the app'
Any information on this would be greatly appreciable. Thanks!
Tested in
Device: iPhone6S+, iOS9.1
Device: iPhone6s, iOS9.4
Update
We had a custom link label for the all the marketing links, which should be kept empty to support Universal Links. The format of the market link would be bnc.lt/«four-letter-identifier»/«link-hash»
I'm adding a note here to help anyone coming across this ticket and thinking they may have a similar issues:
The default Branch link domain for all apps until early 2016 was "bnc.lt." To support Universal Linking, all Branch apps using this bnc.lt domain had entries in a single Apple-App-Site-association (AASA) file. To uniquely identify apps in this AASA file, Branch relied on a four-letter alpha identifier in each link: https://bnc.lt/«four-letter-identifier»/«link-hash»
Branch allows partners to replace the "«four-letter-identifier»/«link-hash»" portion of bnc.lt links with custom aliases ("https://bnc.lt/mylink," for example), however doing so makes it impossible for the app to be identified in the AASA file - meaning that such links cannot function as Universal Links.
Branch introduced app.link domains in early 2016 to replace bnc.lt. The limitation regarding Universal Links and link aliases described here does not affect app.link domains.
I have developed a simple Mozilla add-on which consists of a single open search descriptor XML file.
Now I want to update my add-on with a new project generated by JetPack (still a search engine, but with many other features).
No problem to generate my XPI package, but when I try to publish the new XPI, I got the following error message:
"UUID doest not match the module"
How can I find the UUID of my "opensearch" add-on?
I have no experience with OpenSearch addpms. But since they have no provision for a developer-supplied UUID, my guess is that one is automatically applied when they get published. If my guess is correct then you should be able to find on AMO. Click Edit listing and scroll down to Technical Details, it is the last entry.