open-ear icon indicating copy to clipboard operation
open-ear copied to clipboard

Published 20 hours ago • verified publisher icon ShacharHarshuv

Xiamor Redmi 7 application stucks at startup (v1.6.0, v.1.5.7)

Open dendergunov opened this issue 1 year ago • 2 comments

Good day,

I very appreciate your effort to create a cool open-source ear training app. I use Xiaomi Redmi 7 and I can't launch the application. I've tried version 1.5.7 downloaded from Release pages, version 1.6.0 downloaded from GooglePlay and GetApps

Expected Behavior

The application launches and provides access to its functionality

Current Behavior

v1.6.0

The application freezes at startup showing screen with purple background without any others visible elements (application logo, "loading" hint, etc.). Waiting for dozens of minutes for some further progress didn't change the state of the app.

v.1.5.7

The application freezes at startup showing OpenEar logo with purple gradient background. Waiting for dozens of minutes for some further progress didn't change the state of the app.

Possible Solution

I know it's pain and almost no chance to support any Androird device especially from low-budget segments but I don't have any clue to double check and fix issue from my side. I've given any permission to the app, checked device free storage capcity, etc.

Steps to Reproduce

v.1.6.0

  1. Download the application from GooglePlay / GetApps
  2. Install it, accept giving permissions
  3. Open app
  4. Get stuck

image

v1.5.7

  1. Download the application from GitHub Release page
  2. Install it, accepting installation from untusted source (+ unsigned application)
  3. Open app
  4. Get stuck

image

Context (Environment)

Device model: Xiaomi Redmi 7 MIUI version: MIUI Global 11.0.9 (stable) Android version: 9 PKKQ1.181021.001 Last security update: 2020-10-01

Detailed Description

Ready to give more details or help to diagnose that issue

dendergunov avatar Oct 30 '23 02:10 dendergunov

Hey, this is a web-based mobile app built with capacitor. This issue is likely not an issue with the code itself, but with the capacitor build. If you want to get into it I would start by trying to create a minimal reproduction by building a new app with capacitor. If that still reproduces - try to reach out to capacitor. I would also try to clone the code, update capacitor, and rebuild the app. If it's a capacitor bug it might have been solved in future version.

ShacharHarshuv avatar Oct 30 '23 03:10 ShacharHarshuv

Okay, I'm not a frontend/JS developer and vaguely familiar with JS ecosystem but I'll give it a try. May be if building my own .apk would help I give some feedback

Thanks!

dendergunov avatar Oct 30 '23 05:10 dendergunov