I have a published Google Slides Addon via the G Suite Marketplace SDK. After following the publishing guide everything looked great, until I wanted to bump the version number in the Google Cloud Console via my project's G Suite Market Place SDK Configuration tab.
I entered the number and hit "Save Changes", which put the new version life right away. However, it appears that a couple hours it will always be reset to the same old version (7 in my case). I bumped it again three times and have already tried to update the Chrome Webstore Draft, but it keeps being reset.
Checking the docs, I see no further steps required. I have also not found out yet when the reset occurs, it appears to be "over night" from a European timezone.
EDIT: what may also be relevant, the version in the Google Cloud Console does not automatically update when I publish to the Chrome Webstore. Instead, I manually put the newest version.
This issue should be fixed now.
Also the new publishing flow for GSM, which no longer requires to publish or do changes in the Chrome Web Store, is now live.
Related
My app is in review, received a note stating non-compliant SDK version and I need to deactivate the "wrong" release and upload a new version without the SDK. I haven't found any option to remove it. Is it possible to deactivate releases that are in review? Can you confirm if it's enough to upload new release or am I missing something?
Currently building out a bot in Bot Framework Composer and deploying it on the Teams client. I suddenly am having issues since last week where my custom telemetry ("telemetry - track action") is no longer showing any results in Application Insights. The few that did also only save one property and not the others (see image below). Other events (LUIS, bot message received, etc) all show up in real time and correctly.
The only telemetry event that saved in the past week (there should be at least 10 saved), with only one property logged
The telemetry event and its properties
This is a known bug in Microsoft.Bot.Builder.Dialogs.Adaptive.Runtime version greater than 4.15.0
There is a pull request for this issue and most likely will be fixed in next release of botbuilder-dotnet
PR https://github.com/microsoft/botbuilder-dotnet/pull/6391
A workaround for now is to downgrade the Adaptive.Runtime package to 4.14.0
To learn how to downgrade packages in .NET, here is doc to Install and manage packages in Visual Studio using the NuGet Package Manager
The first version of my extension that I published to the Chrome Web Store was not 1 or 0.1 as initially users were manually installing it. How can I find out which was the first version that was published to the store?
I can't see previous versions in the developer dashboard. "Stats" shows installs over time but not which version they were.
You can see a list of published versions for an extension on https://chrome-stats.com/. Just search for the extension and click on the Download tab. It should have all versions within the past 2 years.
I found some bugs in my code and need to submit a new version.
How do I remove or cancel the old version that is in review in Google Play Console?
I am hoping to not waste Google's time to review something that is already outdated.
[Screenshot of the Issue]
I got the same issue you got when uploading two releases at the same time which both of them were in review mode, the simple answer is "You don't have to worry, the latest version uploaded will get published on Google Play"
You cannot remove versions of your app that you have published on the Google Play console. You can only halt releases for ones that have only been partially rolled out.
Instead, just submit the new version on the track and it will override the version that is in review. As it has a higher version code so it will replace the old version after it has been reviewed and users will download the new version.
I have some xamarin.forms 1.xx( I dont know which version) project on multiple platforms Android and iOS. And I've been asked to upgrade it to the maximum available right now version of xamarin.forms.
Therefore, I have 2 questions:
1) How to determine which version of forms I'm using right now (I'm working in Windows environment using Visual Studio 2015 ).
2) How to migrate/update to newest version of forms? (step by step, if it's possible). I have no idea how the result of that kind of operation supposed to look like, cuz I have never done anything like this before in my life. And what the best practices are?
What I've done is opened VS2015->Help->Xamarin release notes, however there was nothing about version of Forms I'm using. Also, I went to the official xamarin website and there was no guide how to do that. I also tried to look at the release notes the last Forms update and trying to find and fix differences, but my project is so big and I thought that this way doesn't seems right.
I'll answer first the What are the best practice regarding upgrading a Xamarin.Forms application? first and then address your other concerns.
I recently upgraded from 1.5.1 to 2.3.2, and from my experience, this is the steps to go through:
Decide which version you will upgrade from and to.
Read the change logs for all stabled releases between these two versions and look for breaking changes/bugfixes. You can find the release notes on Xamarin's website or on NuGet's website too.
Check regularly for new releases on the Xamarin.Forms forum and check if any reported issues may affect you. Every time Xamarin makes a release, there is a thread full of comments from other developers that may have encountered issues you might be interested in.
Using your favorite versioning software, make sure that all local changes are commited or stashed and create a new branch for your Xamarin.Forms upgrade (you don't know how long the upgrade will take and you still want to be able to send patches during the process)
Upgrade: Read the Important notes at Xamarin.Forms 2.3.2 release notes, especially the When upgrading Xamarin.Forms take care not to simply "update all" as ... part. Remember to upgrade on your PCL project, on your iOS project and on your Android project.
Test your whole app on as many devices as possible and for the longest possible period before you merge your branch back into your development/master/Main branch and address the potential incompatibility issues that may have been created in your development/master/Main simultaneously.
Step 3 is very important as it will allow you to reset back to your starting point and restart if you should fail to upgrade for whatever reason.
Xamarin.Forms is moving fast so it's important that you always keep an eye on what's going on even if you don't upgrade.
Which version am I using right now?
You can check that in the NuGet package interface or in the packages.json file in your project.