microsoft / appcenter

Central repository for App Center open source resources and planning.

Overview

Important

Visual Studio App Center is scheduled for retirement on March 31, 2025. While you can continue to use Visual Studio App Center until it is fully retired, there are several recommended alternatives that you may consider migrating to.

Learn more about support timelines and alternatives.

Contents

Planning

1. Planning Process
2. Roadmap
3. Iteration Plans

Over the past few years our team’s focus has been to deliver a first class DevOps experience for mobile and desktop developers. A substantial part of this journey involved building the next generation of HockeyApp services for our customers. Earlier this year, we completed the HockeyApp shut down. We are now looking at what's next for the App Center service.

Just like any software engineering team, as we focused on building and scaling App Center, we accumulated technical debt that can no longer be sustained. Therefore, as we look to what is next, the App Center team will prioritize improving reliability and performance for the service. This means new feature work will be significantly reduced. Switching focus to reliability and performance wasn’t an easy decision, but nevertheless an important one.

We appreciate all the time and efforts that were put into adding and voting for new features in our GitHub repo. We will continue to monitor your feature requests during this period, but will not be able to commit to a timeframe for addressing them. The following will continue to be true and a priority for the team:

• Customers can continue building, testing, deploying and monitoring their apps.
• We continue to be committed to our SLAs documented here.
• Framework and OS updates will continue to be supported in a timely manner.
• Customer support is still available and free.

Resources

1. Build Script Samples
2. Repositories

Legal Notices

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.

Privacy information can be found at https://privacy.microsoft.com/en-us/

Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.

appcenter's Issues

HoloLens Device Lab

Describe the solution you'd like
iOS and Android device labs with CI/CD make it trivial to automate testing across device families. For HoloLens, no such tools exist. The dream would be able to test builds against different permutations of HoloLens configurations:

• Windows Holographic version (it's currently impossible to downgrade a HoloLens, and pricey to purchase enough to have one at each recent version)
• Commercial Suite (we've found issues that are specific to the commercial suite edition of windows holographic).
• Kiosk Mode options (we have identified and reported numerous confirmed issues that are specific to single app kiosk mode).

With the next HoloLens just around the corner, it's going to multiply the increasingly numerous HoloLens configurations.

Describe alternatives you've considered
We have tried a couple of things, but they simply don't scale. It's possible to keep a HoloLens at a specific Windows version by simply not upgrading. But you quickly run out of devices. It's also possible to install and uninstall commercial suite-- but it takes a very long time. Switching devices in and out of kiosk mode also takes a lot of time (there's also an open bug on this not process being broken to begin with).

Additional context
As we try to support more configurations, the task of testing the configurations is growing too fast. One of our deployments of 75 HoloLenses is constantly struggling to support multiple configurations at once-- the reason being that getting all 75 configured exactly the same at the same time is impossible, even when automating with Intune.

Remove support for TLS 1.0 and 1.1

The industry is moving away from the baseline of TLS 1.0 and 1.1 support onto TLS 1.2. A broader description of support for the protocol can found on our Microsoft Secure blog.

[Feature] Clone branch configurations

What App Center service does this feature apply to?
Build system

Describe the solution you'd like
We should be able to copy build configurations to other branches.

Additional context
Every time we want to create a build from a branch, we need to copy all the configurations. The objective of this feature is to simplify this process.

CodePush to include bundling of pdfs and videos

Appliles to AppCenter CodePush

When developing Cordova apps, CodePush allows us to roll out changes to the app HTML, Javascript and images.

It would be extremely useful for this is include pdfs and videos ie that would be included as part of the downloaded package that could be stored and accessed locally by the app (eg if the device is offline).

Alternatives include using FileTansfer plugins or XMLHttpRequest but these require extra coding and downloading at run time, rather than just when CodePush sends an update.

Push.Token getter property

Due to the many benefits of AppCenter a project is moving to use AppCenter for iOS, Android and UWP.
However one issue with AppCenter being experienced is that limitations of AppCenter push are very restrictive compared to Azure notifications and it seems unlikely that it will change dramatically and that the project will use that feature from the portal any time soon.
Which leads to a dillema, preferable despite that we would like to use the AppCenter Push module due to its simplicity as well as there is more faith in its longevity unlike the many other packages seen.

After inspecting AppCenter SDK and the Push module it seems it is possible but a problem being experienced is that you cannot get the token for push notifications directly, like how you can listen to a notification being received, and in order retrieve/listen to the token one has to intercept the log objects that are being passed around, like with iOS through MSAppCenter.SetLogHandler, and intercept the PushInstallationLog.

Question regarding this is, is it safe/fine to intercept the log like that and get the token, or is there another way, or is it really discouraged?
Like said, would really like use the package and module as well.

Exceptions are grouped up by messages instead of stacktraces

The issue is that all NullReferenceException have got the same messages so they are added to the same group when I look at them on the App Center website. Would it be possible to take into account the stacktrace to group them instead of the message? In my opinion that would make more sense as different crashes happening at different locations ends up in the same group because of that. My workaround was to generate a hash code based on the stacktrace and to prepend it to the message to separate them into different groups.

Allow building off a Git Tag

What App Center service does this feature apply to?
Build

Describe the solution you'd like
We use Gitflow as our branching strategy, and in Gitflow every release is tagged on the master branch. I would like to be able to build off those tags, rather than always building off the HEAD of the branch.

Describe alternatives you've considered
A workaround is creating a new branch off each tag you want a build config for and setting it up as a new build config in AppCenter, which is time consuming.

Additional context
We have multiple customers on different versions of our (white label) app, so being able to build different versions is a must for us.

Expose billing endpoints in public API

Currently, none of our billing API's are visible in swagger, though they are available for use. We'd like to open up these API's for public consumption.

Release to individual testers and multiple distribution groups

Right now on App Center, you can distribute to one distribution group at a time. You would need to re-release to distribute to multiple groups. You also cannot distribute to individual users. You would need to create a single user group to distribute to individual users. This feature will allow users to distribute to multiple distribution groups at once and distribute to individual testers in the portal UI and in the API.

Make it easier to discover Organization billing setup

There is a common issue where a customer has accidentally charged their personal account rather than an org. The outcome of this work will be to redesign/update the billing setup to help mitigate the confusion and also decrease support load.

Send notification to User instead of device

Now that the App Center SDK understand the concept of a user, we will enhance App Center Push to enable developers to send a notification to specific users (rather than devices). This includes sending notifications to multiple devices associated with a user ID.

The following images illustrate the proposed UX for this feature. Please let us know how you feel about them.

An App Center User creating a new notification will see a new *User List option in the wizard.

With that option selected, App Center presents two options:

1. To use user identity provided through the App Center SDK (where the app figures out who the user is, collecting or creating a unique identifier for the user and assigning it to this app instance through the App Center SDK).
2. Use the user's identity as provided by the App Center Identity service.

With the SDK option selected, App Center displays a standard input box used to collect a comma-separated list of user identities. For the App Center Identity-driven option, App Center displays an input box where the user can paste in a comma-separated list of names, but can also use search to locate users in the app's Identity catalog.

Allow setting initial version for "Automatically increment version code"

The "Automatically increment version code" feature is useful for identifying exactly which build testers are using. However, unless your app is brand new, there is a good chance your versionCode is going to be greater than 0, and so the builds created with "Automatically increment version code" will be lower than people are already using. This means that they will have to manually uninstall the existing app before being able to install the newer AppCenter build.

Other CI solutions that have features similar to "Automatically increment version code" also allow you to enter your existing version codes, which allows it to increment using that as a start point. I would very much like to see this feature in AppCenter.

[Feature] Xamarin.iOS extension signing

What App Center service does this feature apply to?
We would like to use VS AppCenter to build our Xamarin.iOS application for iOS devices (Ad-Hoc or AppStore builds, to be technical). Our application includes two iOS extension packages that require additional provisioning profiles to be present during the build process. Unfortunately, at the moment it is not possible: AppCenter allows me to upload only a single provisioning profile:

It was discussed a few times earlier:

• MicrosoftDocs/appcenter-docs#48
• MicrosoftDocs/appcenter-docs#55

Describe the solution you'd like
As a solution: adapt the same approach currently you use in native Obj-C/Swift builds: https://blogs.msdn.microsoft.com/vsappcenter/announcing-ios-app-extension-and-watchos-support-in-visual-studio-app-center/

Describe alternatives you've considered
As an alternative: do not limit clients with a single provisioning profile.

Add support for google-breakpad in Xamarin.Android projects

Using features that are available in AppCenter-SDK-Android and AppCenter-SDK-iOS in Xamarin.Android and Xamarin.iOS projects would be nice. For example added support of google-breakpad for Xamarin.Android projects, that use Android NDK.

Proposal to improve App Center access controls

We hear frequent requests to expand on ways to control access to information, resources and configuration within the App Center portal. While not something we immediately plan to address we would like to start a draft proposal early to start the preliminary planning.

.NET Core Support

Are there any plans to support .NET Core in the future?

Search for diagnostics issues by a user id

Cannot remove HockeyApp nor unlink HockeyApp

After migration to App Studio, I cannot delete the HockeyApp app in App Studio.

[Feature] add automated UI test for UWP apps

What App Center service does this feature apply to?
Testing

Describe the solution you'd like
add automated UI test for UWP apps.

Describe alternatives you've considered
none.

[Feature] Add REST API function for uploading custom crashes

What App Center service does this feature apply to?
AppCenterCrashes

Describe the solution you'd like
API for uploading custom crashes similar to HockeyApp: https://support.hockeyapp.net/kb/api/api-crashes#post-custom-crashes

Feature request: Checking For Updates

I'm using the Cordova Plugin for HockeyApp and I use the in-app update feature that HockeyApp provides:

hockeyapp.checkForUpdate();

This feature should be part of the AppCenter SDK for Cordova.

I understand that I can use CodePush with Cordova Apps, however updating any Cordova plugins requires distributing native packages.

Remove push billing plan options to clarify positioning

App Center Push supports both the Free and Paid billing plans. With the service in Preview, we've never billed customers for Push usage in the Paid tier. Our long term goals include aligning App Center Push with Azure Notifications Hubs, both of which have free and billable usage plans. To simplify things for our customers, App Center Push will become a free service (with the current limitations on Push Audience and batch Push processing). When the customer's needs exceed the capabilities of App Center Push, we'll streamline the customer's shift to using Azure Notification Hubs.

HockeyApp Feedback Service

In Hockey App there is the possibility to have a feedback service, we have started integration with AppCenter (not upgraded from HockeyApp) but would like to have user feedback in-app.

It is not possible to have AppCenter and HockeyAppSDK sidebyside because of the crash reporting native libraries in iOS, however the AppCenter roadmap does not have any indication of the HockeyApp Feedback/Chat system.

Support custom build configurations for iOS

step1, install
npm install appcenter appcenter-analytics appcenter-crashes --save react-native link
step2, do archive in Xcode, but get error in AppDelegate.m

Any configuration issue?

Test

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Lock in Initial MVP Requirements for the Data Sync Service

To complement the new identity service and enable developers to easily manage end-user data we'll be developing a new Cosmos DB backed solution over the coming months. This will be initially targeted towards on-line first apps before layering in additional off-line capabilities. We'll share initial API's and screenshots over the coming weeks.

[Feature] Support the Kotlin DSL, build.gradle.kts

What App Center service does this feature apply to?
The CI/CD build pipeline

Describe the solution you'd like
Instead of only looking for build.gradle files update the project analyzer to also look for build.gradle.kts files.

Describe alternatives you've considered
We're likely looking to move to Travis temporarily for building this app until this feature becomes available. The other alternative would be to revert back to using groovy for build files, but the autocompletion and strong typing of Kotlin DSL are something our team has seen value in.

Additional context
https://github.com/gradle/kotlin-dsl

Add messaging to clarify current 1,000 device audience limit

Currently, App Center allows you to create an Audience of any size, but will only send notifications to the first 1,000 devices in the audience (skipping the remainder). To make this more clear for users, we updated the documentation to clearly state the limitation and describe App Center's behavior when you exceed the limit.

The next step is to update the App Center Push UI so it displays a warning when an audience exceeds the limit. This UI change will affect the Audience pages, but also places where you're sending a notification to an audience.

[Feature] Trigger new builds only upon commits to certain folders within repo

What App Center service does this feature apply to?
This is a feature for git/GitHub integration that would provide more flexibility in build-trigger configurations. I would consider it to be a standard CI feature but apparently App Center is still missing its implementation.

Describe the solution you'd like
When adding an integration to a repository, it should be possible to specify the updates in which folders within the repository should trigger a new build and which not. The configuration should be done in a form of a white-list/black-list (include/exclude) filled with comma-separated folder names. Wild-cards (*) should be available as well.

For every code commit to the build repository, the system would check if there is at least one file from a white-listed folder or at least one file that is not from a black-listed folder. If such a file found, the new build will be started; otherwise the code commit would be ignored as irrelevant to the binary.

Describe alternatives you've considered
Alternative solution would be to separate the code into two repositories--one for the build and one for auxiliary materials--but that introduces additional maintenance overhead. Current setup triggers a new build for every documentation update within the repo, which can potentially cause a queue of useless builds and slow down the development process.

Additional context

Display billing history for services

Enable users to easily see what their monthly usage was for billed services along with relevant billing metrics such as start date, end date, remaining hours, total hours, concurrent devices, etc.

[Bug] `com.android.application` plugin is not detected properly inside Gradle plugin block

Describe the bug
When having the following in your build.gradle script:

plugins {
    id "com.android.application"
}

The configuration (relase and debug) doesn't show up. The plugins block is the recommended way to apply a plugin.

To Reproduce
Apply the android plugin using the plugin block.

Expected behavior
The configuration should show up as expected.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Integrate diagnostics issues with Playfab Game Manager portal

Open up App Center to Playfab so developers can view diagnostics issues directly in the Game Manager portal associated with a player or for the title. When end users report issues in their games, developers will have the ability to open up a players profile to view the crash information.

Make it easier to change/remove Azure Subscriptions

Azure subscriptions are not unassociated from a billed account after it has been connected at some point. This prevents customers from removing a subscription even if they are on the free tier, or never completed billing setup. Additionally, if you go back to billing, it defaults to that selected Azure subscription. This work will get this fixed.

Iteration Plan for February 2019

February 2019 Plan

Kicking off the month of February is work to reduce confusion around billing within App Center's portal. We'll surface more usage information and ease some friction experienced managing your connected subscriptions. Supporting the HockeyApp community while they make the switch to App Center continues to be a strong focus of ours with more key features planned to ship this month.

We're kicking off an initiative to improve your experience working with backend technologies by overhauling our Push service and introducing multiple new services throughout the year. We'll begin sharing designs and mockups for some of the services this iteration to garner early feedback and help you drive the direction of the services towards the future.

Below is a summary of the top level plan items covering the February, 2019 time period.

Services

Billing

• Expose billing endpoints in public API [#5]
• Make it easier to remove/change Azure subscriptions from your account [#6]
• Make it easier to discover organization billing options [#7]
• Display Billing History for services [#8]

Distribution

• Release to individual testers and multiple distribution groups [#10]

Diagnostics

• Search for crashes by an user identifier [#4]
• Integration with Playfab Game Manager console [#2]
• Filter crash and error groups by build number [#55]

Identity

• Create initial designs for the new identity solution [#11]

Push

• Indicate when audiences exceed the existing 1,000 devices limit [#3]
• Remove billing plan options, App Center Push becomes a free service [#9]

Storage

• Create initial designs for the new data solution [#14]

Test

• Support for Appium 1.11

Security

• Deprecation of TLS 1.0 and TLS 1.1 connectivity in favor or TLS 1.2 [#36]

Proposals

• Improving App Center access controls [#13]

ARM64 Support for Crashes (UWP)

Description

Visual Studio 15.8 was released a few days ago which provides ARM64 support for UWP. I managed to target my project to ARM64, and setup the appropriate "RuntimeIdentifiers", but when I build the project I get the following error:

Please build your project specifically for one of the following platforms: x86, x64, ARM

Repro Steps

1. Create a new UWP Project (Visual Studio 15.8)
2. Install the Microsoft.AppCenter.Crashes nuget package (1.8.0).
3. Create a new configuration based off ARM called ARM64.
4. Add <RuntimeIdentifiers>win10-arm64</RuntimeIdentifiers> to the .csproj file to allow building.
5. See Please build your project specifically for one of the following platforms: x86, x64, ARM error on build.

Details

• App Platform: UWP (ARM64)
• SDK Version: 1.8.0

GitLab.com as a source code service

What App Center service does this feature apply to?
We keep a lot of our projects in gitlab.com (online edition).
We use AppCenter on any project that is hosted in VSTS or Bitbucket, however most of our projects are still in GitLab.

Describe the solution you'd like
We want to be able to build an iOS/Android/Xamarin apps from source code hosted on gitlab.com

Describe alternatives you've considered
Alternatives we considered: migrating to VSTS or Bitbucket (these services unfortunately are not on par with GitLab and we will loose a lot of features we use daily for our workflow); using another build service (we use a hosted Jenkins for now - works okay but it is clear future is with AppCenter-like services).

Additional context
I will be glad to provide any additional information

Crash Log Support for HoloLens

Describe the solution you'd like
Much like HockeyApp supported crash logging for iOS and Android projects (including crash log capture, aggregation, symbolication, etc), we are in desperate need of crash logging for HoloLens.

Describe alternatives you've considered
We have tried a couple things:

• MS Store crash logging - The app store can capture crash logs. However, in our scenario we use Intune to manage deploying a line of business app to specific devices in Kiosk mode. These builds cannot go on the store. There is also a way to deploy from the app store to specific private segments-- but this has little support and does not seem to be compatible with Intune. Also, the MS Store does not have graph api endpoints so we cannot automate anything.
• CoreApplication - There's an API that can catch some unhandled errors-- unfortunately it does not catch them all. This is also not a complete solution.

Additional context
Our HoloLens application is used by the public, not by trained users. We have over 6000 visitors per month at a single location (and we are expanding to more). This is not a typical use case for HoloLens but it's proving to be a very engaging one. In order to support more locations, which may be on different versions of the application, different Intune accounts, etc we need to be able to scale the HoloLens software. Crash-logging is a desperate need in this case.

AppCenter Dark Theme

Describe the solution you'd like

• Dark Theme

Describe alternatives you've considered

• Fabric Crashlytics Dark Theme

Additional context

• Screen Shots:

[Bug] Root Gradle build script prevent Appcenter from detecting Android build type

Describe the bug
Given a react native application, having a root Gradle build script which includeBuild (composite build) the android build cause appcenter to not detect properly the build type of android application thus breaking the UI.

To Reproduce
Create a root Gradle build at the base of a react-native application.

Expected behavior
Appcenter should parse the build properly and identify the build type for the android application.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Create initial designs for new identity service

After many requests to better integrate identity into the existing services we've made the decision to begin work on a new identity service to let you get up and running in a matter of minutes. We'll be sharing mockups and design specifications asap while we start laying the foundation.

Correlating custom properties to events

When you set properties with SetCustomProperties, the data is exported to App Insights in a custom event of type CustomPropertyLog with a Properties property like this:

[{"type":"String","name":"Key1","value":"Value1"},{"type":"String","name":"Key2","value":"Value2"}]

What I thought would happen is that the custom properties would be visible on each subsequent event in App Insights, until the custom properties were changed again. That would make it easy to filter the events by context, where the context is defined as the custom properties in place at the time.

As it is, is there some other way in App Insights to correlate custom properties with their subsequent events to enable filtering of events by custom properties? If not, this is an issue that should be addressed.

When viewing events on appcenter.ms, the custom properties don't show up. They should be merged with the specific properties of events, similar to how Microsoft.ApplicationInsights.TelemetryClient.Context works. The docs I found don't lend any insight into what custom properties are for other than "various purposes" which include push notifications. The implementation and docs look like they need updates.

SetUserId for Analytics events

It's not clear what scope AppCenter.SetUserId applies to. It is documented anywhere? When I set it, I don't see any user IDs in my events exported to Application Insights. A post today mentions user IDs in the context of crashes, but not events.

It would be useful for the user ID to be incorporated into both AppCenter's dashboard for events and its export of events to Application Insights.

Version 1.13.0

[Bug]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Support handled errors in react native

It may be that I've missed something in the doc but I'm not able to find how I can manually send an error.

[Bug] Incomplete stack traces ("hidden" references) in App Center builds (iOS)

Describe the bug
I am encountering a lot of hidden stack trace lines in my crash reports when I build my binaries using the build feature.

To Reproduce
Steps to reproduce the behavior:

1. Build an iOS app with App Center for internal distribution (an AdHoc provision profile).
2. Produce a crash in the app.
3. Go to the crash report, observe "hidden#00000" references.

Expected behavior
A full stack trace with file, function names and line numbers.

Screenshots

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
My application has bitcode generation ON. From the documentation, it is recommended to turn this feature off as Apple reserves the discretion to rebuild your app which might invalid the stack trace. However, in my case this was an internal build, not for the App Store. I also made sure that the debug dSYM files are generated (DEBUG_INFORMATION_FORMAT = "dwarf-with-dsym"). Builds from the App Center also don't allow you to download the full archive, only the ipa file, so there is no way to reconcile the missing references. What are the steps and settings needed to produce a full stack trace when crashes happen from builds made in App Center?

[Feature] GitLab as bug tracker service

What App Center service does this feature apply to?
Services (Bug tracker)

Describe the solution you'd like
At this moment only GitHub, Jira and Azure DevOps are available as bug tracker. Hockey App allows more types.
For our transition form Hockey App to App Center it is required to have GitLab as bug tracker service included in App Center.

Describe alternatives you've considered
No alternatives

Logging metrics using custom events

The properties object in the custom events tracking lets us track useful properties and aggregate them (and show count and other useful data). Would love to see the same being extended to metrics as well. Similar to what the Application Insights SDK supports.

Our scenario involves sending a few important numbers as metrics for an event. We're using properties as a workaround right now but that isn't useful since numeric values have a larger range and don't show up how we would like them to.

Essentially looking for something like this:
TrackEvent("My Event", Dictionary<string, string> properties, Dictionary<string, double> metrics)

Links for AI SDK TrackEvent with metrics:
https://social.technet.microsoft.com/wiki/contents/articles/31192.custom-telemetry-events-with-trackevent-in-microsoft-application-insights.aspx
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-api-custom-events-metrics#trackevent

Cordova: Support for Handled errors

Reporting of Handled errors is currently supported for Xamarin only.
Would be nice to have this for Cordova (and other platforms also).
Nothing special is needed, just same functionality as exists for Xamarin

[Feature] Support for multiple flavor dimensions

At the moment App Center does not support multiple flavor dimensions (Android). We only get the cross product of each flavor + build type but not the cross product of flavors belonging to different dimensions + build type. Please add this feature to ensure we get the same build variants like in Android Studio.

Report handled errors for React Native apps

Description (feature request)

Allow generating crash reports for handled errors similar to the capability built into bugsnag-react-native. Our app makes heavy use of this in a top-level component with React 16's (relatively) new error boundary concept. Any chance this capability has made its way to the roadmap yet?