tikilittle at gmail.com
Tue Feb 28 15:14:48 CST 2012
Thanks for articulating this catch-22. It's something that I had a gut
sense of, but am now slightly reassured that there are others with similar
We will keep you updated if we get any new ideas.
> Message: 24
> Date: Tue, 28 Feb 2012 08:40:30 -0500
> From: Thomas McGrath III <mcgrath3 at mac.com>
> To: How to use LiveCode <use-livecode at lists.runrev.com>
> Subject: Re: iPhonePickMedia .m4p
> Message-ID: <E013E5F9-E094-4441-BE20-6BE38BF331FB at mac.com>
> Content-Type: text/plain; charset=windows-1252
> I had a different problem with iPhonePickMedia but not with .m4p files.
> For me the problem was that certain songs could be listed in the library
> but not really be there physically and yet they were not available to
> download via iCloud either. It was as if they were in-between being
> downloaded from i-cloud and living on the device. They could not be deleted
> These songs would cause the app to quit after choosing a playlist or group
> of songs that included one of these files. The solution was to turn off
> iCloud on the device and then turn it back on and then the offending songs
> were gone. The icon on the song in the device was the downloading icon
> (outside circle with a square in it).
> The reason I am posting this here is that it is very hard to release an
> app knowing there is a case where it will crash and yet if you reveal that
> particular issue during the publishing process you will be rejected. If you
> don't then people will give poor reviews because you didn't let them know
> about the condition beforehand. A catch 22?
> With this in mind I do not think the iPhonePickMedia, as it is now, can be
> used in any apps that are to be published on the App Store. This therefore
> is a blocking issue although it works on 'normal' downloaded songs and
> 'normal' iCloud songs.
> -- Tom McGrath III
> 3mcgrath at comcast.net
More information about the use-livecode