Is there any need for a 1536 x 2048 folio anymore? Do they even work with DPS v32?

Question

So I just received a gig from a client to design their new magazine issue using their provided back issue indd DPS files (CS6), along with their new content from the latest print edition that will fill these articles. However, the previous DPS documents were built using 1536 x 2048 pixel (vertical orientation) pages. Is there even a use for this folio size anymore? And would it even work with Apple and Google Play and the latest folio buider?
I recall in 2012, I had to build two renditions during the iPad1 to retina transition, so it could be read on both devices. But I thought Adobe soon abandoned the need for two renditions and went with just the 1024 pixels. I've only worked with 1024 since with all my other clients. Is this correct thinking? Do I need to convert these files to 1024? I'm guessing so, but I don't want to just guess.
The other thing I wonder is if Apple had approved their back issue on 2048 pixels, would it mean a re-submission the new folio using 1024 px height? We have to update the App to iOS 8 anyway, so I just need to be sure I'm working with the folio size.
Can I assume the v32.2 folio builder is solid enough to run with at this time? Hoping one folio will work with both storefronts (google play and Apple) without any glitches/scaling issues.
Cheers,
Brian

Answer 1

I think I'll advise my client to convert their current 2048 pixel folio to 1024 pixel height. Then have that 1024 build approved by Apple. Then push my new issue content into the approved App shell. The only time I needed a 2048 rendition is when the new retina iPads came out (mid-2012), and we wanted to take full advantage of the resolution. We also used a 1024 rendition for the iPad1s.
I suspect their 2048 folio is what is making their App in Content Viewer crash. Also, they didn't have a V or H in the filenames, which is what I was trained to do with naming each of my articles, so perhaps that's what's making it crash? I was surprised it would even upload/recognize an article without the V or H in the filename.
Does this sound like possible solution to fix the crashing? The other thing I noticed is that they didn't package their files with fonts and links for each article like I would (They had 20 indd article docs in one issue folder, then all images for all articles were in one links folder (named images, not links. Another suspect. Does Adobe prefer "Links" for the assets?).
If I could solve their crashing problem, I'd be their rock star.
Brian