Non-existing folio in viewer app

Hi.
Strangely my newly created viewer app shows a folio what is not in DPS server.
It was deleted from the server some times ago.
Why it still shows up in new app?
Ants

I'm having this same problem with published Android apps.  The main folios within these apps weren't updating on our Xoom.  They were updated in Folio Builder and then confirmed to be changed on digitalpublishing.acrobat.com and using the Adobe Viewer app, however the folios would not show an "Update Available" message in the published Android apps.  The only solution I could get to work, without contacting users and telling them to delete the app and redownload it, was to create a new folio from the same files and publish it with a cover image and title that indicated it is newer.  The user will have to archive the old ones themselves to dump it from their devices.  The problem is that even though I've unpublished and deleted the old folios, and tapped "Archive" on our Xoom, they are still showing up in the library with the "Download" button.  How can we get rid of these old folios to try and reduce confusion.  My original folios were created pre v20 so I'm assuming their age was the problem with simply being able to update them.  The same updates to the iPad renditions of these folios have updated on an iPad2 without issue.
Andrew

Similar Messages

  • The app references non-public selectors in viewer.app/viewer: consume:

    Hi there,
    I note a previously answered question on this topic further down, but wanted to check this again in light of the recent updates.
    We have re-built the app again (today) as per the instructions and now run into this error only (previously two) as part of submitting through Application Loader.
    Is it still safe to ignore this error (as per Neil's instructions) and submit if this is the only flag, given the update to cover iOS 8?
    Many thanks in advance.

    You can ignore this warning.
    Neil

  • Applescript Utility insists on non-existent Script Editor.app 2.1.2

    I recently got Script Editor to work after years of being bugged (was a 4 step process ending with replacing the resources folder in the package). It hadn't worked across several OSX clean installs, so there's no clue to what caused the corruption.
    Now, even though the Editor works, Utility only has 2.1.2 in it's pulldown. I have tried numerous times, including with a shut-down, to get this to "Select" the working Editor (2.1.1), but even though it is selected through the file-selector, it never gets set in the pulldown. The utility is 1.0. I've also checked system archives from 1, 2, and 3 years ago, and there has never been a version 2.1.2 on the computers we use.
    Will Applescript work properly with this incorrect listing for a non-existent version, and therefore unlocatable Editor? It would be very foolish to start writing scripts if the foundation upon which they are written is still fundamentally damaged. And will the only effect of this be that all Editor access must be done by clicking on an icon or alias?
    --Thanks

    The '2.1.2' version, which is only 404 kb, does not launch. Version 2.1.1 opens correctly and is 12.4 mb. Also, version '2.1.2' has a generic application icon (the pencil/paintbrush-A over blank document) whereas the 2.1.1 version has a script/pen icon if that helps. Both versions are, however, 2.1._ (either 2.1.1 or 2.1.2), not 2.2._, which I believe is the Leopard version that you had mentioned.
    I can't say for sure that this folder/app hasn't been in my finder for a while or not as it has only been as of this week that I switched my Finder's view from the standard icon view to 'columns' view without preview icons (that's how I noticed the duplicate folders with the same names stacked on top of each other). Thanks again for all your help.
    Best,
    John

  • Is there a way to organize shared folios in the content viewer app?

    I have quite the collection of folios that have been shared with me. My list has grown quite a bit and it's getting harder to find certain folios in the Content Viewer App on my iPad. The ordering seems to be somewhat random. Is there any way to organize the list of folios? Bonus Question: Any way to create folders and place certain folios inside of folders?
    Thanks!

    Use library filters.

  • Questionable NE (non existant) row in conflict view

    In the conflicts view, we have a record which shows up as non existing in the base version. But we know that the row existed (in LIVE) before the child workspace was created, and we know that the row was subsequently updated (not inserted) in LIVE and updated (not inserted) in the child workspace. (We have the history view). Why would the conflict view think that the row didn't exist before?<br>
    WM_WORKSPACE PK WM_DELETED
    <br>GR13_M4_2005Q3 1039133 NO
    <br>BASE 10391336     NE
    <br>LIVE 10391336 NO
    <p>
    Thanks
    chaim

    Hi,
    This could happen for the following reason. If the update in LIVE workspace overwrites the base version of the row, then the CONF view will report the row as being non existent.  The NE code does not mean that the base row never existed, only that it no longer exists.  Since the base row was overwritten, the CONF view is correctly identifying it as NE.
    The row in the LIVE workspace could be overwritten due to the table being versioned with the view_w_overwrite history option or without any history. It is also possible to turn overwrite on at the session level for tables versioned with the view_wo_overwrite option.
    This behavior would typically not occur in workspaces that are not continually refreshed(CR). This is because when a non-CR workspace is created, an implicit savepoint in created in the parent workspace which will prevent the base row from being overwritten. This savepoint is not created for CR workspaces. You could also explicitly create a savepoint in the LIVE workspace if you want to prevent this situation from occurring.
    If any of the above is not applicable to your case, then I would need more details to determine why this is happening.
    Regards,
    Ben

  • Adobe Content Viewer app and .folio file

    I created and published a .folio file on my Web server.
    My boss downloaded the free Adobe Content Viewer app from iTunes for his iPad. When he tries to open the .folio file from his home screen it goes online to a browser and just shows a grey screen with an icon for the .folio file, its file size and nothing happens.
    Am I missing something? The same .folio file works fine on my desktop version of Adobe Content Viewer. How do I get it to work in his app?
    Thanks.

    Found some other threads. Is this right?
    1. Create my .folio file.
    2. Host on my free Acrobat.com account.
    3. Get viewer to get their own free Acrobat.com account and share doc URL with them.
    4. They download file and view in the free Adobe Content viewer app for iPad.
    Would check, but I don't have access to an iPad with live internet connection (yet).
    Thanks.

  • Opening a page of a Folio in a Multi-viewer app is possible by URL Scheme

    I set URL Scheme on Multi-App by Viewer Builder.
    It launches well by tapping the URL Scheme button on Web page.
    Is it possible to open a page of a folio in a Multi-viewer app is possible by URL Scheme?
    Shimoawazu

    if you can find your app's actual URLscheme in the info.plist file inside the viewer, you can deep link into your articles (you also need the internal names of your folio and the articles), I find out here:
    http://forums.adobe.com/thread/1009059
    —Johannes

  • How do I add content to a Multi Folio viewer app?

    We have created a multi folio viewer app, but cannot get our folios to appear in the app. We've published both with the same Apple ID. Help! What are we doing wrong?

    The folio is set to Public Free.
    The Title ID matches the email address used to publish content.
    However, in the Folio Producer, we can't make the 'Product ID' match the com.mydomain etc. from the 'Apple Bundle ID', as Folio Producer doesn't allow us to enter the dash [-] in the name...

  • Folio producer tools update required to use folio builder but content viewer app not available

    Hi,
    I have a problem with DPS Folio Producer tools.
    We are unable to use Folio Builder to update our iPad presentation to the cloud because we keep getting this message: An update is required to use Folio Builder. Please click here to download Folio Producer Tools.
    We have previously done this only to discover that the new version of Folio Producer Tools is incompatible with the Content Viewer and the new Content Viewer app is not yet approved, or available from Apple.
    So we have done a rollback to a previous version of the Folio Producer Tools which worked for a few hours, but is now prompting for the update again - but as explained above we cannot download the update until the Content Viewer app is available.
    HELPPPPPPP!!!

    This is the DPS model.
    When a company thinks first about monetizing solutions instead of making it an extra option.
    You are not free anymore to use the tools you want, you must follow Adobe's decisions to update online apps.
    Online apps are everything but good.
    You will have to wait until the Viewer gets approved by Apple.
    Dear Adobe: do you see how many people come here because they don't understand how your technical model works?

  • Non-existent errors in Problems view

    Hello,
    Sometimes flash builder shows non-existent errors in Problems. "Project clean" helps, but errors appear after several compilations again.

    The problem was in pure action script class that extented MXML component.
    After deleting that code all problems were dissappeared.

  • Ipad previewing - content viewer app

    I have a folio which I am able to preview on my PC Content Viewer software, but will not seem to update on my iPad Content Viewer app.
    I am running Folio Producer 12.2.4 on CS5.5.
    I have updated the app to the most up to date version from the App Store. I have also tried uninstalling and reinstalling the app from scratch. It still won't load on my iPad!
    Are there any common reasons for this that I can investigate? I have a pitch to deliver using the app at the end of the week - which if successful could mean investing in the DP Suite to a greater extent than we are now - but not if I can't preview the fruits of my testing!
    All advice appreciated!

    I must say that's not my experience. I wish every piece of software I use had  forums like this where within half an hour of posting a problem I had a solution. I couldn't care less if the solution is pretty or not, so long as it works.
    Software companies can't win. They release something new this way, with an accompanying support forum, and they're accused of beta testing by proxy. They release something new, say it's finished and let us get on with it, and they're accused of not testing the product enough first.
    I haven't paid a penny so far -  all the folio testing I've done has been done for free. The plan is to pitch the concept to my company on the basis of what I've developed so far and if they go for it, then start paying. I won't put the money into something like this without being sure that some form of support exists. So far so good as far as I'm concerned!
    And thanks again, Bob.

  • Folio crashes viewer on Android

    Hi everyone,
    We tried both "Adobe Content Viewer" and "DPS Tips" apps for Android on the HP TouchPad running CyanogenMod 7.1 Android Alpha 3.
    And got two problems so far:
    1) There is problem to sign in with existing Adobe ID in the "Adobe Content Viewer" app - it fails to authenticate few times but then finally gets through.
    2) Then opening of the folio (any even simple with no overlays) crashes the app with this error:
    "The application Adobe Viewer (process air.com.adobe.contentviewer) has stopped unexpectedly. Please try again".
    First we thought it's CyanogenMod distro problems but then read that others also had same problems but on the different Android devices:
    https://market.android.com/details?id=air.com.adobe.contentviewer&feature=search_result#?t =W251bGwsMSwxLDEsImFpci5jb20uYWRvYmUuY29udGVudHZpZXdlciJd
    Few questions:
    1) Is there stable Android device that is working flawlessly with "Adobe Content Viewer"? What devices/Android versions are used by Adobe for development/testing?
    2) Are there any Android system settings that could be tweaked so the Viewer app will not crash on the opening of folio? Is there any table exist with Viewer app/device compatibility/issues or list of supporting devices?
    3) Is there any Air app that could be used for testing what Air functionality is working on the specific Android system and what doesn't? Or are there any other tools/logs available to troubleshoot the problem?
    Thank you for the help,
    Gennady

    No, the documentation doesn't go into specifics about which HTML/web views work and which ones don't. The program team is currently working on improving this area.

  • Opening Folio Crashes Viewer on Android

    Hi guys,
    We tried "Adobe Content Viewer" and "DPS Tips" apps for Android on the HP TouchPad running latest CyanogenMod 9 (Android 4.0.4): cm-9-20130512-NIGHTLY-tenderloin.zip
    And still have the problem when opening the folio crashes the app with the error:
    "Unfortunately, Adobe Viewer has stopped".
    First we thought it's CyanogenMod distro problems but then read that others also having the same problem even on the popular Samsung Galaxy Tab, please see that review below.
    Anything could be done so it will start to work? Is there non-Air version currently in development?
    Thank you,
    Gennady
    https://play.google.com/store/apps/details?id=air.com.adobe.contentviewer
    "A Google User - February 11, 2013 - Version 3.0.0.0.69658
    Samsung Galaxy Tab
    Login and download fine, but crashes as soon as you open any publication. Update 02/11/13: Still crashes as soon as you open a publication on both my galaxy nexus and galaxy tab (Both Running Jelly Bean). Once it tries to open it and it crashes it tries to open and crash the same folio until you uninstall and reinstall the app.  During the attempted cases of reopening the app sometimes the initial view of the folio will load but quickly crash. Really wish this thing would get fixed."

    Is the live viewer/app in Google Play below V25? If so, update your app to the latest V26/V25 Viewer. There were significant changes made in V25 to avoid this type of crashing behaviour.
    **CyanogenMod crashes are not supported. If you have an incident reported from your customer who is running a stock OS, contact DPS Gold Support.

  • "Your script uses objects from a non-existent collection"

    I have a multiple page form with a barcode on each form.  I created a separate collection for each barcode.  The auto generated code looks fine and has the correct collection created, however I still get the error, Paper Forms Barcode error "Your script uses objects from a non-existent collection".
    I'm not sure what is wrong and I don't know how to fix it.  Anyone else run into this?

    You will need to create a shared folder in Dropbox, then populate that with what ever folders you need to organize the files. It appears the DropBox app,will not handle this, but you can do, it by logging in to you account via Safari. Once the folders are created, they will show up in the app. Likewise with designating the folders as shared. Anyone you wish to share with will need a Dropbox account. (using the public folder will not work since links out it are for files only, not folders. An odd restriction, but it is what it is).
    IF you have copies of the files on a PC, you will find that will be the easiest place to upload them from. If they are only in iBooks on the iPad, you will need to synch and use the file management function to copy them off. not sure if you can synch them back over to DropCopy within iTunes (never tried it).
    DEpending on your needs, a couple of apps to look into are iCab Mobile (a browser), and GoodReader (doc viewing and management app). Both integrate well with DropBox.

  • Distribute publication via Adobe Viewer.app on iPad?

    Is there anything to stop someone from publishing a publication via the Adobe Viewer.app on the iPad? I realize this wouldn't be ideal, since it's a non-branded viewer, etc., but legally, is this "against the rules"?

    Sorry, maybe I gave the wrong impression.
    What I meant was, is there anything against my sharing a publication via the Adobe Viewer.app on the iPad. I'm not talking about sharing an IPA, I'm talking about sharing the publication within the Viewer.app. For example, I create the publication in InDesign and once it's complete, I then "Share" it via the Folio Builder panel to the people I want to share it with (roughly 50-60 people). Then, using their Adobe ID, they could log in, via the Viewer.app on the iPad, and download the publication to their device.
    Again, not ideal since it's not branded (ie. you have to access the publication via the Viewer.app), but it's a free solution. Not that I'm looking for a free solution, but since doing what I've been asked to do by my client — ie. release a 1-off, in-house app via an iOS Enterprise Developer Account — requires a minimum $50,000+ buy-in for the Adobe DPS Enterprise Edition subscription, this seems like my only option (outside of not using the Adobe DPS).
    Thoughts?

Maybe you are looking for