-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
[@nativescript/imagepicker]: Migrate to Android photo picker #605
Comments
The deadline is January 22 2025 for this migration. Any idea how can we fix this easily? |
Here it the original blog post about this change from Android: https://medium.com/androiddevelopers/permissionless-is-the-future-of-storage-on-android-3fbceeb3d70a |
I gave it a short try to show this newer Android PhotoPicker, but as I have not much experience in native Android app development, I am not familiar with the newer "registerForActivityResult" approach. I was already failing during the first step of creating the imageLauncher.
So I tried to move that into the activityCreatedEvent
But this crashes with the following message:
Actually registerForActivityResult should return an instance of ActivityResultLauncher, but for some reason I get an instance of ActivityResultRegistry Maybe somebody with more experience in Android development can help out here. |
@triniwiz Is this something you want to tackle? |
I'm still experiencing the same issue and haven't found an alternative solution or any open PR addressing this fix. |
I have just written a short explanation in the description form seen in the screenshot. Haven't been a problem and not getting any warnings for now, but this plugin should definitely be migrated to the new api |
This is the warning im getting on every playstore release now:
"If your app has a one-time or infrequent need to access photos and videos, migrate to the Android photo picker"
The text was updated successfully, but these errors were encountered: