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

A workaround for issue#929 #948

Closed
wants to merge 2 commits into from
Closed

A workaround for issue#929 #948

wants to merge 2 commits into from

Conversation

hybcloud
Copy link

according to issue #929, native app cannot start successfully under such development tools and environment:

Android Studio Flamingo | 2022.2.1 Patch 2
Build #AI-222.4459.24.2221.10121639, built on May 12, 2023
Runtime version: 17.0.6+0-b2043.56-9586694 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 1280M
Cores: 16
Registry:
    external.system.auto.import.disabled=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    gradle.version.catalogs.dynamic.support=true
SDK: 33
NDK: 25.1.8937393
device: Samsung S970+

after this fix, the application can start and seems to perform correctly, but it might need someone experienced to check it twice so that it does not harm in respect of any other aspects.

@hybcloud hybcloud force-pushed the main branch 2 times, most recently from 23e9290 to d674088 Compare December 5, 2023 15:20
@hybcloud hybcloud changed the title a probable bug fix for #929 A workaround for issue#929 Dec 5, 2023
@hybcloud
Copy link
Author

hybcloud commented Dec 5, 2023

The problem is not solved 6 months after it was reported and given a "solution". I wish the issue could be taken into consideration asap.

@DanAlbert
Copy link
Member

Sorry, there hasn't actually been anyone able to look at this repo in quite some time. I'm doing what I can to volunteer some time for clean up.

A few other PRs (and at least one bug, I'm still sifting through and am sure I'll find more) also addressed this. After talking with a handful of folks, I don't think this fix is correct. #1000 seems to be the right fix.

@DanAlbert DanAlbert closed this Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants