microG and googleplay package name conflict
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
My learning machine cannot install the original Google Play suite because of the Android Enterprise Device Manager. However, after I installed it, MicroG could not verify the Google signature but verified the signature set at work. To solve the signature, Google Play must be installed, but they cannot coexist. Is there any way to solve it? There is another problem. The account on the device cannot be opened without modifying the file. These are the problems I encountered.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported coexistence problem between microG and the original Google Play suite on an Android Enterprise device. Investigate the package-name and Google-signature verification behavior, then check how the account-opening failure relates to the required file modification. Done would require a clearly defined compatible installation and account flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100