Hey guys, using this codepen example on iOS Safari the IVSPlayer.isPlayerSupported flag is true but the sdk doesn't handle timed metadata. Is there no support for this feature on iOS Safari (i did not find any information about this in the documentation)? And how can i detect support of timed-metadata if not with this flag? Thx!

Hi @svenmalkus, timed metadata is currently unsupported in iOS Safari but we're working on it

Hi @linhphan534 - it sounds like you got it working, but if you need further support on this topic, could you please file a ticket in the AWS Support Center so we can take a deeper look at your broadcasts? Thanks!

When attempting to upgrade AmazonIVSPlayer in my project to version 1.2.0, I see the following error:

missing required architecture x86_64

It compiles just fine when I keep it at version 1.1.0.

I'm going to close this for now, please reopen if the issue persists.

Hey guys, using this codepen example on iOS Safari the IVSPlayer.isPlayerSupported flag is true but the sdk doesn't handle timed metadata. Is there no support for this feature on iOS Safari (i did not find any information about this in the documentation)? And how can i detect support of timed-metadata if not with this flag? Thx!

hi @iannparker thanks for you response. I listen for the state Player.State.ENDED then I postpone in a short period of time before calling my own retry mechanism. I tried a number of differences of delayed time (10s, 20s, 30s, 40s, 50s, 60s) I tried both player?.play() and

player?.load(Uri.parse(url))
player?.play()

I realized that only the second one works after 60s of delayed time.

Hi,

Could you provide more details about your retry mechanism? If you restart the stream by calling load() and play() on the player once the broadcaster has resumed broadcasting the stream I would expect the stream to resume as normal.

We are also actively working on automatic network recovery in a number of situations and hope to deliver this in an upcoming release.

Hi @anooj1483, with IVS android SDK, rendering the video to a specific surface is available. However, IVS doesn't support 360 video by itself (ex - IVS doesn't support spatial metadata, or anything particular to support 360 video and also hasn't been officially tested with 360 video)

hello, I working with your player a while, currently I got an issue, if streamer got a network problem in short time (such as switching from wifi to 4g or vise vera ) the player goes into the buffering state, after a while it goes to playing state or even ended state, in both cases the viewer is frozen. If I implement a mechanism to retry, it take me almost 1 minute to replay.

Is it possible to stream 360 videos and play it in IVS player?

Thanks for the report. Where are you seeing this error specifically? For some background, please provide:

1. The output of bundle exec pod env
2. The build output, exported by:
   1. Showing the report navigator<br>
   2. Selecting the build that failed<br>
   3. Clicking the "Export..." button, saving to a file or the clipboard<br>

When attempting to upgrade AmazonIVSPlayer in my project to version 1.2.0, I see the following error:

missing required architecture x86_64

It compiles just fine when I keep it at version 1.1.0.

When attempting to upgrade AmazonIVSPlayer in my project, I see the error:

missing required architecture x86_64

It compiles just fine when I keep it at version 1.1.0.

When attempting to upgrade AmazonIVSPlayer in my project, I see the error:

missing required architecture x86_64

It compiles just fine when I keep it at version 1.1.0.

We released a fix for this in 1.2.1: https://docs.aws.amazon.com/ivs/latest/userguide/IVSPRN.html

Thanks again for reporting this issue.

Bumps ini from 1.3.5 to 1.3.8. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/npm/ini/commit/a2c5da86604bc2238fe393c5ff083bf23a9910eb"><code>a2c5da8</code></a> 1.3.8</li> <li><a href="https://github.com/npm/ini/commit/af5c6bb5dca6f0248c153aa87e25bddfc515ff6e"><code>af5c6bb</code></a> Do not use Object.create(null)</li> <li><a href="https://github.com/npm/ini/commit/8b648a1ac49e1b3b7686ea957e0b95e544bc6ec1"><code>8b648a1</code></a> don't test where our devdeps don't even work</li> <li><a href="https://github.com/npm/ini/commit/c74c8af35f32b801a7e82a8309eab792a95932f6"><code>c74c8af</code></a> 1.3.7</li> <li><a href="https://github.com/npm/ini/commit/024b8b55ac1c980c6225607b007714c54eb501ba"><code>024b8b5</code></a> update deps, add linting</li> <li><a href="https://github.com/npm/ini/commit/032fbaf5f0b98fce70c8cc380e0d05177a9c9073"><code>032fbaf</code></a> Use Object.create(null) to avoid default object property hazards</li> <li><a href="https://github.com/npm/ini/commit/2da90391ef70db41d10f013e3a87f9a8c5d01a72"><code>2da9039</code></a> 1.3.6</li> <li><a href="https://github.com/npm/ini/commit/cfea636f534b5ca7550d2c28b7d1a95d936d56c6"><code>cfea636</code></a> better git push script, before publish instead of after</li> <li><a href="https://github.com/npm/ini/commit/56d2805e07ccd94e2ba0984ac9240ff02d44b6f1"><code>56d2805</code></a> do not allow invalid hazardous string as section name</li> <li>See full diff in <a href="https://github.com/isaacs/ini/compare/v1.3.5...v1.3.8">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~isaacs">isaacs</a>, a new releaser for ini since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps ini from 1.3.5 to 1.3.8. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/npm/ini/commit/a2c5da86604bc2238fe393c5ff083bf23a9910eb"><code>a2c5da8</code></a> 1.3.8</li> <li><a href="https://github.com/npm/ini/commit/af5c6bb5dca6f0248c153aa87e25bddfc515ff6e"><code>af5c6bb</code></a> Do not use Object.create(null)</li> <li><a href="https://github.com/npm/ini/commit/8b648a1ac49e1b3b7686ea957e0b95e544bc6ec1"><code>8b648a1</code></a> don't test where our devdeps don't even work</li> <li><a href="https://github.com/npm/ini/commit/c74c8af35f32b801a7e82a8309eab792a95932f6"><code>c74c8af</code></a> 1.3.7</li> <li><a href="https://github.com/npm/ini/commit/024b8b55ac1c980c6225607b007714c54eb501ba"><code>024b8b5</code></a> update deps, add linting</li> <li><a href="https://github.com/npm/ini/commit/032fbaf5f0b98fce70c8cc380e0d05177a9c9073"><code>032fbaf</code></a> Use Object.create(null) to avoid default object property hazards</li> <li><a href="https://github.com/npm/ini/commit/2da90391ef70db41d10f013e3a87f9a8c5d01a72"><code>2da9039</code></a> 1.3.6</li> <li><a href="https://github.com/npm/ini/commit/cfea636f534b5ca7550d2c28b7d1a95d936d56c6"><code>cfea636</code></a> better git push script, before publish instead of after</li> <li><a href="https://github.com/npm/ini/commit/56d2805e07ccd94e2ba0984ac9240ff02d44b6f1"><code>56d2805</code></a> do not allow invalid hazardous string as section name</li> <li>See full diff in <a href="https://github.com/isaacs/ini/compare/v1.3.5...v1.3.8">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~isaacs">isaacs</a>, a new releaser for ini since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Hi @rjaylwar, thanks for reporting this issue. We are working on a fix now with a target release date of next week. In the meantime, if possible, we recommend targeting a previous Android API level. As you mentioned, this issue only occurs on Android 11. Thanks again.

When you try and connect on a non-wifi connection the IVS player crashes.

Likely Cause: Probably related to the android 11 behavior changes for the TelephonyManager#getDataNetworkType() method which requires the Manifest.permission.READ_PHONE_STATE permission.

This is a regression because the crash does not occur in version 1.0.0 but it does occur in version 1.2.0. https://developer.android.com/reference/android/telephony/TelephonyManager#getNetworkType()

CRASH LOG: A/com.ivsapp: java_vm_ext.cc:577] JNI DETECTED ERROR IN APPLICATION: JNI CallObjectMethodV called with pending exception java.lang.SecurityException: getDataNetworkTypeForSubscriber java_vm_ext.cc:577] at java.lang.Exception android.os.Parcel.createExceptionOrNull(int, java.lang.String) (Parcel.java:2373) java_vm_ext.cc:577] at java.lang.Exception android.os.Parcel.createException(int, java.lang.String) (Parcel.java:2357) java_vm_ext.cc:577] at void android.os.Parcel.readException(int, java.lang.String) (Parcel.java:2340) java_vm_ext.cc:577] at void android.os.Parcel.readException() (Parcel.java:2282) java_vm_ext.cc:577] at int com.android.internal.telephony.ITelephony$Stub$Proxy.getNetworkTypeForSubscriber(int, java.lang.String, java.lang.String) (ITelephony.java:8762) java_vm_ext.cc:577] at int android.telephony.TelephonyManager.getNetworkType(int) (TelephonyManager.java:3021) java_vm_ext.cc:577] at int android.telephony.TelephonyManager.getNetworkType() (TelephonyManager.java:2985) java_vm_ext.cc:577] at com.amazonaws.ivs.net.NetworkLinkInfo$CellularNetworkType com.amazonaws.ivs.net.NetworkLinkInfo.getCellularNetworkType() (NetworkLinkInfo.java:97) java_vm_ext.cc:577] at java.lang.String com.amazonaws.ivs.net.NetworkLinkInfo.getNetworkType() (NetworkLinkInfo.java:70) java_vm_ext.cc:577] java_vm_ext.cc:577] in call to CallObjectMethodV A/com.ivsapp: runtime.cc:655] Runtime aborting...

Updating the README with step by step instructions for setting up the repl.it live demo.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Description of changes: Removes a metadata callback method from the BasicPlayback example. This callback is never invoked, and its apparent intended functionality is handled by the IVSTextMetadataCue case above it.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Description of changes: Removes a metadata callback method from the BasicPlayback example. This callback is never invoked, and its apparent intended functionality is handled by the IVSTextMetadataCue case above it.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.