Android Target SDK version is 33, but should be 32 or lower (targetSdkVersion in AndroidManifest.xml).
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, firebase, unity
- Domain
- mobile-dev
Research direction
Start with the AndroidManifest.xml targetSdkVersion mentioned in the report and reproduce the problem by generating an APK from the listed Unity and Firebase versions. Upload it through Meta Quest Developer HUB and compare the resulting target SDK with the required Meta Quest limit; done means the generated application is accepted without the target-SDK error.
Written by the indexing model from the issue text.
Description
[READ] For Firebase Unity SDK issues, please report to Firebase Unity open-source
Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.
[REQUIRED] Please fill in the following fields:
- Unity editor version: 2022.3.27f to 2022.3.37f (Possibly more older versions.)
- Firebase Unity SDK version: 11.8.0 to 12.1.0
- Source you installed the SDK: .unitypackage
- Problematic Firebase Component: firebase-analytics-unity/firebase-auth-unity/firebase-firestore-unity
- Other Firebase Components in use: _____ (Auth, Database, etc.)
- Additional SDKs you are using: Meta XR SDK
- Platform you are using the Unity editor on: Windows
- Platform you are targeting: Android - Meta Quets
- Scripting Runtime: IL2CPP
[REQUIRED] Please describe the issue here:
TARGET_SDK_VERSION_TOO_HIGH
Android Target SDK version is 33, but should be 32 or lower (targetSdkVersion in AndroidManifest.xml).
Steps to reproduce:
The problem always occurs when I try to upload the application to the Meta board, but as a really curious note, the application is launched in the Meta Quets viewer and I can use it without problems.
What happened? How can we make the problem occur?
Generating the APK and then trying to upload it through Meta Quest Developer HUB
Does anyone have a solution to compile with Firebase that is using API level 33 to be able to use it with a 32 like the Meta Quest?
It's going to be a real pain, since I have client registration set up without the need for email, a function for client auth with Meta and Firestore for player data.
// TODO(you): code here to reproduce the problem
- Dominant language
- C#
- Stars
- 923
- Forks
- 456
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from firebase/quickstart-unity
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
firebase/quickstart-unity#1448 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
firebase/quickstart-unity#1432 · 1 comment ·
-
new
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
firebase/quickstart-unity#1411 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/quickstart-unity#1403 · 1 comment ·
-
Firebase or specific Android versions trigger app_clear_data on first_open, disrupting our funnel Opennew
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/quickstart-unity#1390 · 1 comment ·
All issues in firebase/quickstart-unity
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·