5/29/2023 0 Comments Deploymate![]() > skip ahead request GET /audio/mbw/mbw0340/mbw0340.mp3 HTTP/1.1 > request from start: GET /audio/mbw/mbw0340/mbw0340.mp3 HTTP/1.1 The following examples are done with Charles debugging proxy. It appears that some combination of redirection and/or headers in the response disable the random access functionality in iTunes for these specific podcasts and it no longer sends the range header. I also tested the same problematic podcasts with the iOS Podcasts app 1.2. Also Some do a redirect for tracking downloads, some don’t. It does not make a difference whether or not the podcast uses m4a or mp3 format. When you click on the track iTunes seems to be sending the Range: header to state the position requested on the podcasts that work. I can provide you with the list of my tests. I checked 10 other podcasts and found a second one that has the same issue with iTunes. playback continues stubbornly, no HTTP ranged request for new position is sent.playback should skip to the clicked position.now click in the playing control progress track to try to skip to a later point.double click on any older podcast episode, it will start to play at 00:00.In iTunes: File – Subscribe to Podcast, enter.Skipping forward in mp3 podcasts is broken. ITunes 11.0.2: Skipping Ahead Broken in Some Podcasts Summary By baking such a tool into the Xcode IDE it would save us this embarrassment. That such functionality is possible is proven by a newly released app called Deploymate () which scans an Xcode project and flags such problems.įrom personal experience I can say that even though we developers KNOW about having to check for these scenarios and also test on older supported iOS versions it DOES happen and the result is always embarrassment for having shipped an app that crashes. respondsToSelector) and point out code where a crash is inevitable. The IDE should detect scenarios where the developer forgot add the appropriate checks if functionality exists (e.g. Xcode: Provide Warnings if App might Crash on devices with previous iOS versionĬompiling with “Latest SDK” allows developers to make use of new functionality in the latest SDKs, but if the deployment target allows for execution on earlier iOS versions then there are many scenarios where usage of new functionality or even constants might lead to a crash.
0 Comments
Leave a Reply. |