Buttons with multiple actions doesn't work in v32.1

We are having the same error. It happens both with buttons and with auto-playing MSOs. It affects almost all of our published folios and results in content not appearing at all to the end user. We're not looking forward to releasing v32.1 to the public to fix the current download problem and only upset them by providing folios with missing content.

This does not sound like expected behavior.

I've shared both your issues with the team for investigation.

Hi Jiri,

I sent you a direct message requesting more information.

Thank you,

Michelle

Hello WebbieMac,

I am looking into this with an article with 2 slideshow MSOs set to auto play. I am able to reproduce that the 2nd MSO does not auto play I have updated the bug with this information for our developers.
Are there more problems you're seeing?

Thank you,

Michelle

Thanks, Michelle. We appreciate the help! We're also having an issue with auto-play videos not stopping on the last frame. They play once fine, but if you swipe down and view another video in the same stack, the auto-play videos are no longer on the last frame on the previous pages. The other problem that we're having is that you can't pinch and zoom pdfs from HTML Resources anymore.

Hi WebbieMac,

Thank you for this information. I'll take a look when I receive your files for investigation.

Michelle

hello, I'm also having problems with the buttons on the MSO, they do not work when clicked to display the image. Slow to respond, seems to become locked. The same folio worked perfectly before the update. This will be fixed next update on this?

Hi Lilicuca,

Could you please send me more information on the MSO that you have that do not work? I am unable to reproduce clicking a button and having the MSO respond correctly. Please feel free to message me directly with this information.

What version is your folio?

What version is your app?

Could you describe to me how you set up the MSO?

Thank you,

Michelle

Hi Michelle, is the following, I am developing catalogs of shoes to some customers based so my folios of image galleries. The buttons of the galleries are thumbnails of shoes that appear when clicked model. Since the beginning of last year I have developed and everything worked fine, after upgrading from ACV these buttons do not work instantly like before, it seems to catch and only after some time it works but if I change the page it happens again. I've done several tests changing the version of the publication and nothing. I'm using the ACV 32 and 8 IOS configuration MSO is "go to state" and I select the state according to the image. Tested in other ipads and the same happens. If you want I can send you a file to share some folio. Thank you for listening.

Have the same problem here updating a previous app for a customer to run on iOS8. In this app we have "pulsating" buttons as MSO linking to different pages or states. Unfortunately this folios work well in the content viewer (v32.0.2) but the buttons are not shown in the development ipa generated with the latest app builder. All the buttons are not shown in the app - if I read the problems above it might be the problem, that the auto-play doesn't work if the buttons are faded out at the beginning… now testing with different settings in folio overlay slideshow panel…

Christian

Hi Lilicuca,

If you don't mind sharing a folio, I'd like to take a look. Please direct message me.Is it possible to take a screenshot of what you should see and a screenshot of what you're seeing now?

Michelle

I had an similar issue with one of our magazines

Index-Page with 3 Slideshow MSOs that have also a link on them to the article.

Works on iPad Preview via cable, works on the content viewer for iOS but as soon as I build the exact same Folio with the latest DPS Builder Tools on Mac, only ONE of the three slideshows autoplays. I had to remove the functionality completely!

So, I tried to change the settings for the slideshow on several ways, but the problem still exists. For your Info: To Update the Single App I created a new Folio with PDF-based articles and imported the old InDesign documents into these articles step by step. In these documents I also changed the slideshows to vector-based format…

Thanks for help!

Christian

Please see also following thread for screenshots of my problem with dps v32.1

MSO Problems with DPS v32.1 app builder and content viewer

Hello,

was there any resolution to the problems with MSOs in DPS apps when being used on iOS 8 updated devices?

We've had similar problems where complicated MSO's (with buttons with more than one function) that worked fine on iOS 7 test iPads no longer work on iOS 8 test iPads. This is especially problematic as I had used MSO's to make the videos in the app start on one image, end on another and have a button to 'skip/play' the video by using a button that takes the user to a mso which is an image of the video's end frame or to a mso where the video plays on load. I have 10+ of these videos in the iPad app.

Any help at all with this would be gratefully received. I'm concerned I'm going to have to redesign half of the app and compromise the functionality and userbility of the App just to be able to get it to work on iOS 8, which would be a great shame as it all worked really well on iOS 7.

many thanks,

Chrissy

Hi Chrissy,

I think this is not an iOS8 Problem but more a problem with the actual dps v32.1 built. I've updated an app before on version v32.0.2 and this workes fine on iOS8 and the content viewer with the same version. there are only problems with the new version, which also appear with the release of the new iOS content viewer today… hope there will be a fix shortly - I think there will be a lot of more problem when the people update there Content viewer whithin the next days…

Christian

Hello Michelle,

I was wondering if you were able to see my post today about problems with MSO's and whether you were able to get any solutions for the previous posts on this thread?

I have been in contact with the Adobe support team with regards to the problems I am having with the App I've created  and sent the App and some sample indesign files for them to look over. They have been really unhelpful and just given me this as the response:

I have also researched about this issue and would like to inform you that there are several changes which have been incorporated in iOS 8.

So apps which are created and working with iOS 7 might not work with iOS 8. This is an expected behavior.

You would have to create the app again with compatibility settings with iOS 8 and then release an update for the same.

So altogether there has to be another to be app created for iOS 8.

As we are already 2 weeks over deadline, due to problems with iOS 8, and out of budget to cover the extra work we have had to do so far problem solving these issues, I really hoped for something better than this response.

Are Adobe really not looking into a fix for this? Is the only solution to limit the interactivity and functionality of DPS apps so they work within the new restrictions of iOS 8?

Any help would be really gratefully received.

many thanks,

Chrissy

hello, I still have the same problem with no response. I sent messages to Michelle and not heard back.

Small hint: With the lates Adobe Content Viewer Update for iOS I notice the Splashscreen switching from landscape to portraitmode for a second. This also never happened before. With my newly built app on 32.1 I can see the same behaviour.

Hello,

We met the same issue for a client.... it's very complicated for us, because we presented several MSO in the same page, with autoplays and other animations by Edge with texts mso which don't work anymore...

but now how can we go through that issue ?

1- correct all of our pages considering 1 unique MSO / page ? and simple script button ?

2 - or wait for the Adobe content viewer's update till all work fine again ? but for how long ??

Please which solution do you recommend ?

Thanks.

Nicolas

I would like to hear an update from Adobe on this bug as it causes problems accessing and displaying content in past published folios. Should we expect a fix soon? Thank you!

The engineering team is working on a fix for this. in terms of timing, I'm hopeful it is included in the next public dot release (early next week). the adobe content viewer in the App Store would be several days later because of the apple approval process.

I've now tested the folio on an android-tablet with the adobe content viewer and there the folios work well – it seems the problems are iOS-only.

Can anyone confirm this?

Hello Nathan, if I need to provide my folio and Indesign files for you analyze.

So im guessing from reading through this we should wait on updating our app again as we are having issues with auto playback on v32 also.

Whats with the large number of bugs recently? We had a 5 star app which we then updated to help with the iOS8 problems. This then got a slating as loads of people can't use it due to another bug, and now in building it for v32 we are encoutering new bugs with existing and new folios. This makes us look bad to our clients we are dealing with, as we keep having problems and missing deadlines.

Is the estimated time for a bug fix next week, and then the time for apple to approve new apps?

Hello all,

I know there are several issues here, but they may all be related to the same underlying bug(s). We know that having these problems fixed is very important, but it takes some time to understand what each of you are experiencing since there are so many variables. There are a couple of things that are fixed for our dot release as Nathan commented and these may fix your individual problems.

WebbieMac, your auto play bug has been fixed and is in testing.
Jiri Mraz, I have not been able to repro the original report from you.

I have sent info to several of you where you can drop examples of your files and information I need from you about what you're doing.

I've been out of the country since Friday and I'm catching up with your comments. While I was gone devs and other testers have been investigating the auto play MSO bug and testing around various MSOs.

Michelle

This issue has already been reported and fixed.

Hi Chrissy,

The team has been investigating and fixing MSO bugs. Where possible, we can check some customer content. The fixes are stated to go out in our next release early next week as Nathan posted above.

Michelle

Hello Jiri,

Thank you for your content. We were able to repro some problems and I have entered a bug to the dev team.

Michelle

Hello Michelle,

thanks for the feedback, fingers crossed all is better next week!

Chrissy

Adding my experience to the mix as well. The way our app was developed utilized a handful of MSOs on each page at any given time, which meant the v32.1 release essentially crippled the app. We use one of the MSOs for the in-folio navigation (instead of the built in viewer nav) so you literally couldn't navigate away from the first screen. Pretty big bug for us!

Another bug I seem to be having now is with OAM files.

I have done this effect a few times before so I know this has worked before. Im trying to have a panel animate off the screen revealing the indesign layers behind. My Background is set to transparent in both indesign and edge, and my poster image is the first frame. Autoplay obviously doesn't work yet, but when I tap to play, the object moves, but then reveals the poster image behind still, no transparent frame?

I'd like to contribute one small thought to this discussion: I've noticed in the past that if I set a button to have more than one "go to state" action, if the mso's that are referenced by those actions have "cross-fade" turned off, the the button won't work. But if you enable cross-fade on the mso's, then the button actions do work. Might this be a contributing factor to some of the inconsistencies people are experiencing?

Hello Michelle

thanks so much to Adobe for fixing that bug. I have just rebuilt the app with the app version and everything works as it did before iOS 8. I am so relieved!

Chrissy

The fix for this was released on Monday afternoon Seattle time.

Neil

Hello,

The auto-play function doesn't work for me either. And I did the upgrade this morning. What can I do to make it work?

Hello user_magazine,

what did you upgrade this morning? if you try to see it in the content viewer on iOS8 - I think the fixed version of the content viewer hasn't pass the approval process of apple yet. so the content viewer is the "old" v32.1. if you are building an app with the app builder and test the .ipa file on iOS8 it should work. i've done the test a few minute ago and the problem (on my folios) is fixed now… I think the new content viewer will be available end of the weed / next week as an update in itunes…

christian

Great - just created a new .ipa and tested it on iOS8 - the MSO problems are fixed and the folio behavior is as expected… thanks!

christian

I have the same problem overhere. A plain simple on/off circle as MSO doesn't work. This in one of the most basic forms of interaction, and it just doesn't work.

The strange thing is, it works in preview on the desktop folder, but not in preview on the iPad, or after uploading it in the Folio Builder.

I really hope that this issue can be solved asap.