-
Notifications
You must be signed in to change notification settings - Fork 41
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
Player is never ready #102
Comments
I also only see a resize event being sent via post message. No events with |
I had the same problem with the version X from the CDN. I forked the repo into https://github.com/EngineeringKiosk/podigee-podcast-player/tree/development, updated all dependencies, compiled it and using a local version now. You can find a working version of the player.js events here: https://github.com/EngineeringKiosk/webpage/pull/81/files#diff-1f17be1ad22cddc1e0bfcf3389eaba97c2bdde4df4434641e699a4c806424a34 |
@andygrunwald I am having the same problem and tried your fork, but that didn't help me unfortunately. I actually don't see any changes in your fork which could fix that? Do you have any other hints for me on how you got it working with your fork? |
I just realized what the issue is: Podigee has a new CDN which is https://player.podigee-cdn.net. So you need to use that one instead of https://cdn.podigee.com. |
@mgrsskls If you clone https://github.com/EngineeringKiosk/podigee-podcast-player, ensure to use the branch Install the dependencies: make init Build the package: make build Then you can get the updated javascript package from the |
When executing:
const iframe = document.createElement('iframe');
iframe.src = 'https://researchvr.podigee.io/92-researchvr88/embed?context=external';
document.body.appendChild(iframe);
const player = new playerjs.Player(iframe);
player.isReady stays false even when the player is ready.
When testing here I also can not get the event to work:
http://playerjs.io/test.html?url=https%3A%2F%2Fresearchvr.podigee.io%2F92-researchvr88%2Fembed%3Fcontext%3Dexternal
The text was updated successfully, but these errors were encountered: