Those two sentences are not contradictory: new file plugin is broken on iOS by default.. by throwing an exception on initialize.. unless this new <preference> is set in the app's config.xml (which signals that the dev researched the issue and addressed it accordingly).
The migration step to preserve existing behaviour is to set that preference with the legacy location (value="documents", right?). value="library" is a better option for new applications, or existing applications that migrate those old files to new location manually (imho probably not worth the effort / risk, but the option is there). The docs will be clear about what to do / which preference value to set, and Ian is even looking into printing a message during plugin install time through CLI to help guide users to making the right choice, even if they ignored the blog posts and plugin docs etc. On Thu, Jan 23, 2014 at 12:10 PM, Marcel Kinard <cmarc...@gmail.com> wrote: > These 2 sentences seem contradictory, or am I misunderstanding? > > On Jan 23, 2014, at 11:52 AM, Ian Clelland <iclell...@chromium.org> wrote: > > > File plugin will be *broken by default* on iOS. > > On iOS, CDVFile will throw an exception on initialize if this isn't set. > > The reason I ask is because I'm trying to figure out if there is a > required migration step for appdevs to preserve the existing behavior.
