Hi Folks,
Just to spread the word: if you wanted to add crash reporting to a Windows 10 app that you’ve created with Juce, this is finally possible. Arrived last week!
I had my first crash report through for a Windows 10 store app created with Juce this morning - great stuff.
Best to all,
Pete
I’m curious, @peteatjuce, does your app distribution include the debug symbols?
I’ve managed to include the debug symbols in the .msixbundle before submitting to the MS Store. But once published and installed from the MS Store, the .pdb file is not present.
Thanks
Hi @mmurphy!
Thanks for asking. No, it doesn’t.
Rather, our solution some time back was to adopt sentry.io for our Windows crash reporting, which seems to work well and was easy enough to integrate. NB: we use a post-build script to upload the debug symbols to their server.
On iOS, macOS and tvOS we rely on the system’s built in crash reporting. Xcode uploads the necessary data to the App Store for TestFlight, which we use for test app distribution.
On Android, we now use Firebase for both crash reporting and app distribution. We use a script to upload our Android symbols.
Best wishes,
Pete
Thank you, @peteatjuce!
This is all very useful information!
Happy to help!
Best wishes, Pete
@peteatjuce is your windows store app standalone only or does it ship a plugin as well?
i’m curious if one can use the windows store to ship a standalone + plugin like the apple store does with auv3.
Hi @modosc !
It is an app with VST3.
Our solution was to include the VST3 as a binary asset.
When you run the Wotja app, the app compares the VST3 version with anything pre installed, and will prompt to install/update accordingly.
It is an approach that has worked very well for us.
If you install the free Wotja app from the Microsoft Store, you can see the process in action!
Best wishes, Pete
