I'm currently working on my first Teams App which means modifying the manifest.json through the Microsoft Teams Developer Portal. Whenever I make changes and try to update the application through "Preview in Teams" or "Publish to org" it doesn't update to the most recent version.
When I modify the app configurations and version and try to update or publish the application. The changes aren't reflected. When I go to "Apps" in the sidebar and click on my app that is installed and look at the version, only the old version is shown.
Is there a way to make sure MS Teams pulls the most recent version? I tried even quitting teams and opening it again. I have also tried downloading the package and installing it from the package. Still the same version.
Related
I'm uploading an app manifest into App Studio that's an older version (happens to be 1.5), but when I try Install it using App Studio, it fails. When I go to the schema editor inside App Studio, it shows me it's changed it to Schema Version 1.9, which I think is the issue.
Incidentally, this user is having a similar-but-different issue: App Studio is generating a version 1.9 manifest which fails validation and stops side loading earlier today.
We are able to repro the issue. Raised a bug. We don't have ETA to share when it will be fixed.
Please follow this Git-hub for updates on bug.
I haven't been able to install any applications I create using App Studio since yesterday afternoon (Oct 5 Us/New_York time). When I try to install directly from App Studios I get a "Manifest parsing has failed" error message. If I download the package and try to upload it to the team I get a generic something went wrong error message.
Im having this issue with all my applications including those I haven't made any changes to.
I am running Microsoft Teams Version 1.3.00.24758 and App Studio version Version 1.5.1
App studios is setting the manifest's to version 1.8
I have the same issue when I run teams in developer preview.
On a side note: I notice that App Studio now has the option to create a Team tab for a Meeting. Which I believe is in preview right now and not officially out. I don't remember seeing that earlier in the day. Maybe App Studio was recently updated?
thanks in advance. I've been working on a Xamarin app that I hope to market before too long. It's at the stage where I'd like to share it with one or 2 beta testers on Windows 10. however, I am unable to run the app outside of Visual Studio (where it works fine). When I try to click on the relevant debug or release .exe in Windows Explorer nothing happens. How can I let my beta testers try it without having them install VS and giving them the entire project?
If you have registered a Microsoft developer account and paid for it, then you can add your tester's Microsoft account to the console, then you upload your app to the console, they can see it in the store for testing.
Otherwise, you can make an offline bundle file using the visual studio publish wizard. For more info, see the details.
We've hit a few cases recently were we have wanted to upgrade local database data structure or the user settings and we've almost broken backwards compatibility.
How do people test there development "Work In Progress" with a
released version of an app?
Do you update your AndroidManifest and
Info.Plist versions after each release? We are currently just
setting them at the time of creating the IPA and that change is not
added back into the repo
I want to automate the release for my xamarin iOS and android apps into the stores. I was wondering, if I can use fast lane tools via VSTS to do it.
Right now I directly add the playstore step in VSTS to deploy the android app into playstore. But, I want to make use of snapshot,snap grab, spaceship, supply and various other fastlane tools. Is it possible? If yes can anyone provide steps of how to do it? I tried searching the marketplace in vsts but the fastlane tools are not available.
Thanks.
FYI, VSTS released extensions to release iOS app on App Store or test flights.
Extension
Microsoft Visual Studio Team Services (VSTS) and Team Foundation
Server (TFS) use fastlane in their Apple App Store extension.
Getting Started
Once you have created or retrieved credentials for
your App Store account, then perform the following steps to automate
releasing updates from a VSTS build or release definition:
Install the App Store extension from the VSTS Marketplace
Go to your VSTS or TFS project, click on the Build tab, and create a new build
definition (the "+" icon) that is hooked up to your project's appropriate
source repo
Click Add build step... and select the
necessary tasks to generate your release assets (e.g. Gulp, Cordova
Build)
Click Add build step... and select App Store Release from the
Deploy category
Configure the App Store Release task with the desired
authentication method, the generated IPA file path, and the desired
release track.
Now when you build, your app will automatically be
published to iTunes Connect!
Fastlane Docs