Iteration Plan for May 2020

[ahdbilal]

May 2020 Plan

Last month, the App Center team updated various frameworks across our services (Android NDK, Appium, Sparkle) to support the latest versions of each respective framework. The team also made structural changes with our distribution upload client, as a result of which we expect users to get improved and reliable upload speed performance. The improved service will be rolled out to all users this month.

This month, we have the following features planned:

API

• Introduce App-level API tokens [API token per app and per feature #167]

Distribution

• Roll out improved upload speed capability to all App Center portal users
• Improve deep linking to release experience [Link to Release on install.appcenter.ms #140]

SDK

• Package iOS SDK as SPM [App Center SDK as a Swift Package for Xcode 11 #1295]
• Add support for Mac Catalyst [Add support for mac Catalyst #1578]

[phatmann]

Could we please get #125 into this iteration? It is seriously hurting our workflow, and will not take long to implement. Thanks!

[ahdbilal]

Thanks @phatmann for the feedback. I have just pushed for it internally and will share an update soon.

[jasmsu]

Was "Insights into versions affected by same crash group" that was a part of the April 2020 plan dropped? Looks like it wasn't marked as done in April.

[imWildCat]

Anything which the community can help to support mac Catalyst?

[tdekoning]

@ahdbilal any update on ticket #125 being in this iteration plan?

[phatmann]

Could the dev team provide some insight into how issues are chosen for an iteration? Many top-rated issues are ignored month and month, while others are addressed much sooner. What is the criterion for selection? I for one have become increasingly frustrated with the lack of progress on fundamental aspects of App Center and wonder if this is just how it will be indefinitely.

[phatmann]

To provide a little more data, the majority of the most-commented issues are well over a year old.

[zoontek]

Could you take #1575 as well? Currently, the module is unusable with Error Boundaries and graceful crashes.

It would be super useful to catch unhandled Promise rejection (by overriding https://github.com/facebook/react-native/blob/0.63-stable/Libraries/Promise.js#L19) and custom non-fatal error too (by overriding ErrorUtils global handler)!

We are currently using Crashlytics for this, but would love to remove it.

Even without the deep integration, just adding a function that allow to send a custom error with a certain severity would be amazing and I guess it's not that much work 😕

[Mikilll94]

Any update on #125 (Google Play internal test track support)?