Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppCenter Retirement: How to handle .NET MAUI Apps? #2625

Open
thomasgalliker opened this issue Mar 15, 2024 · 8 comments
Open

AppCenter Retirement: How to handle .NET MAUI Apps? #2625

thomasgalliker opened this issue Mar 15, 2024 · 8 comments
Labels
feature request New feature request

Comments

@thomasgalliker
Copy link

Visual Studio App Center is scheduled for retirement on March 31, 2025. Learn more about support timelines and recommended alternatives.

What is your proposed migration path for Xamarin Forms and .NET MAUI apps that use the AppCenter features Build, Analytics, Crashes, Distribution? Please post your ideas below.

@thomasgalliker thomasgalliker added the feature request New feature request label Mar 15, 2024
@huyphams
Copy link

Please open source self-hosting appcenter.
#2623

@Xynratron
Copy link

We integrated the Builds completly in our Azure Devops Pipelines.

Application Insights seems not to be a good replacement for Analytics / Crashes - any other Ideas?

The Distribution is the biggest Problem, because Microsoft Partner Center Apps & Games is a mess and not updated in years (as far as I can see). After anouncing the retirement for Microsoft AppStore for Business, what ist the roadmap for distributing Windows Applications?

@thomasgalliker thomasgalliker changed the title AppCenter Retirement AppCenter Retirement: .NET MAUI Apps Mar 15, 2024
@thomasgalliker thomasgalliker changed the title AppCenter Retirement: .NET MAUI Apps AppCenter Retirement: How to handle .NET MAUI Apps? Mar 15, 2024
@thomasgalliker
Copy link
Author

Does anyone have experience with aptabase? It seems to have tracking features. Not sure about diagnostics/crash analysis. It's open-source and free for self-hosting instances.
https://github.com/aptabase

@LathanHarper
Copy link

It's the diagnostic logs I will miss the most!

@LathanHarper
Copy link

We integrated the Builds completly in our Azure Devops Pipelines.

Application Insights seems not to be a good replacement for Analytics / Crashes - any other Ideas?

The Distribution is the biggest Problem, because Microsoft Partner Center Apps & Games is a mess and not updated in years (as far as I can see). After anouncing the retirement for Microsoft AppStore for Business, what ist the roadmap for distributing Windows Applications?

for Enterprise distribution the InTune product is actually really awesome at that. When a device (or PC) is enrolled you get your
own "store" plus all the normal remote admin ability.

@thomasgalliker
Copy link
Author

Does anyone use Sentry for .NET MAUI analytics and/or crash reporting?

@softlion
Copy link

softlion commented May 3, 2024

Does anyone use Sentry for .NET MAUI analytics and/or crash reporting?

Yes me. Work perfectly with Apple App Store apps. Better than appcenter crash. Full C# stack trace.

Also, for building I tried Azure Pipeline, but in the end switched to codemagic.io
Codemagic supports the latest macs (M1 M2) and the latest xcode versions. They release new versions fast, you can still select older versions.
M1 are free. Build time is 10mn total.

@thomasgalliker
Copy link
Author

Good news. I migrated my MAUI app from AppCenter to Sentry. It‘s pretty cool! We mainly use the crash reporting and user tracking part.
All distribution related task will be done with native Android/iOS tools (question: does anyone have scripts to upload apps to the stores?).

Here you have a small MAUI demo app with Sentry integration: https://github.com/hsrcasnet/MauiSamples/tree/main/MonitoringDemo/MonitoringDemo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature request
Projects
None yet
Development

No branches or pull requests

5 participants