You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently we have sort of a bridge between web codebase and iOS-native code. This bridge helps us in controlling some very specific cases. For example:
if user plays a podcast, from the bridge we will get the information in iOS, and then iOS native code will play the podcast using notification manager instead of playing it in website-webview.
if user plays a video, the bridge passes the information to iOS, and then iOS native code will play the video in new full-screen activity.
Now currently for podcast the information can be sent from web-code to iOS native but we cannot send information from iOS native to web-code.
To Reproduce
Steps to reproduce the behavior:
Go to any podcast
Play the podcast
Once the podcast plays in iOS it will be visible in notifications section of the iOS os.
Pause the podcast in notification.
Notice that the app still shows pause icon in website.
Expected behavior
As soon as we pause the podcast in notification, the change should be reflected correctly in web-code base too.
Similar Issues
If we remove the podcast by clearing the notification, the website still shows as if the podcast is playing, the bottom podcast bar in website should get terminated.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently we have sort of a bridge between web codebase and iOS-native code. This bridge helps us in controlling some very specific cases. For example:
Now currently for podcast the information can be sent from web-code to iOS native but we cannot send information from iOS native to web-code.
To Reproduce
Steps to reproduce the behavior:
pause
icon in website.Expected behavior
As soon as we pause the podcast in notification, the change should be reflected correctly in web-code base too.
Similar Issues
The text was updated successfully, but these errors were encountered: