-
Notifications
You must be signed in to change notification settings - Fork 30
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
Picture-in-Picture Fix #151
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of asks here on the PR. Additionally we are currently working on a PR to address some of the functional differences between PiP usage on Android vs iOS.
android/src/main/java/com/amazonaws/ivs/reactnative/player/AmazonIvsView.kt
Outdated
Show resolved
Hide resolved
Sounds great, I hope my changes are compatible, having some control over pip is a huge deal at my company since it'd create strange behaviors, for example: We use "track player" like lib to control and execute background playback; without any control, the pip would automatically start and duplicate the playback audio. |
android/build.gradle
Outdated
compileSdkVersion getExtOrIntegerDefault('compileSdkVersion') | ||
buildToolsVersion getExtOrDefault('buildToolsVersion') | ||
defaultConfig { | ||
minSdkVersion 21 | ||
minSdkVersion 26 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we're getting a build issue here:
https://github.com/aws/amazon-ivs-react-native-player/actions/runs/5904085265/job/16025249877?pr=151#step:11:817
example/android/build.gradle
Outdated
targetSdkVersion = 31 | ||
minSdkVersion = rootProject.ext.minSdkVersion | ||
compileSdkVersion = rootProject.ext.targetSdkVersion | ||
targetSdkVersion = rootProject.ext.targetSdkVersion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately it seems example android project can't access rootProject's data.
a880bed
to
4cb711b
Compare
@dawhitia Not sure why the android e2e tests are failing |
I cleared the build cache and re-running 👍 |
currently tracking down the root cause here when trying to run the build on emulator. |
It looks like Soloader is missing, I've noticed it isn't specified in build.gradle's I'm not sure if there are other required steps to run detox tests aside from a specific AVD name, but I wasn't able to run it locally, unfortunately. |
Considering we haven't been able to determine the root cause here, can we split the RN 0.73 compatibility into its own PR ? |
Can you let me know what is blocking you? Currently it expects the emulator to already be running before running for build |
adds control over pip behavior, can be enabled or disabled
4cb711b
to
8dc65a9
Compare
Agreed! FYI I've merged the changes and fixes related to PIP into a single commit. |
@dawhitla I've fixed the android build errors, all checks are now green. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the patience on this 👍
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.