-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
bug: App Update Android - API level 33 getPackageInfo(String, int) deprecated #131
Comments
Thank you for reporting this. PRs are welcome. |
…eprecated as of API 33: Android 13.0 (Tiramisu). capawesome-team#131
I made the change but how can I can test Android plugin code within Android Studio like hitting a breakpoint. I don't have experience with Capacitor plugin development. Thanks! |
Take a look at the Capacitor and Android Studio docs: |
Thanks @robingenz. I made the change, tested it on a physical Anroid API level < 33 and it works but I got the error |
Feel free to create a PR. I will then take a look at it. |
I have created a pull request. Let me know please. |
…eprecated as of API 33: Android 13.0 (Tiramisu). capawesome-team#131
* #33 PackageManager.getPackageInfo(packageName, 0) is deprecated as of API 33: Android 13.0 (Tiramisu). #131 * #33 PackageManager.getPackageInfo(packageName, 0) is deprecated as of API 33: Android 13.0 (Tiramisu). #131 * docs: add changeset --------- Co-authored-by: Robin Genz <[email protected]>
Plugin(s)
Version
5.0.1
Platform(s)
Current behavior
@robingenz - I noticed
getPackageInfo(packageName, 0);
form the this line of codereturn this.getContext().getPackageManager().getPackageInfo(packageName, 0);
has to been updated to reflect deprecation note for API 33 as per this SO issue https://stackoverflow.com/questions/73388061/android-13-sdk-33-packagemanager-getpackageinfostring-int-deprecated-what.Am I missing something?
Thanks.
Expected behavior
...
Reproduction
...
Steps to reproduce
...
Other information
...
Capacitor doctor
...
Before submitting
The text was updated successfully, but these errors were encountered: