Anh
Anh
How should we plan the release on both the Play Store and GitHub? Apart from the new benchmark, we've also made bug fixes and added new features. Considering these changes,...
In most cases, the Play Store version (AAB) and the APK should behave the same. However, there have been instances where the Play Store version crashed while the APK didn't....
@Mostelk Should I create a new Github release and upload the APK with the same build number as in Playstore? Or should we release a new version with the updated...
@AhmedTElthakeb Can you provide a screenshot? Or give more detail like which device, app build version you tested?
@Mostelk @freedomtan I just discovered this one. https://www.browserstack.com/private-devices They launched it [recently](https://www.browserstack.com/press/browserstack-launches-private-devices-to-meet-enterprise-security-and-customization-needs). It's exactly what we need.
--- We currently use the `mobile_update` branch, which contains commits related to enforcing a maximum duration. This is not in the `master` branch. Therefore, we have 3 options: 1. Merge...
https://github.com/mlcommons/inference/tags
- https://github.com/mlcommons/inference/pull/2394/
> This probably conflicts with #1040 to some extent. Whichever is merged first will require merging master into the other and some adjustments (and resolving some merge conflicts) will be...
- The Browser Stack test is already run automatically when merged into the master branch. - I think the release note should not be included in the app; else, we...