URGENT*  Multi-Folio viewer problem(s)

I went to design school to avoid situations like this.
I have my Development App built and loaded. I got my Free Public issue to load perfectly. I can not seem to get the retail issue to appear & I'm not sure where I'm going wrong. Can somebody help a poor designer try and get this up and running so I can submit? I'm running late already and I do not have a head for the more programmer-esque aspects of the development process.
Thanks in advance.

I believe so. All content (Free & Retail) shows up flawlessly in the Content Viewer, but the retail piece does not show up in the App. The App does not have a place to sign in in the upper left. The Free/Public content shows up fine. Could this have something to do with the Secret Handshake? Does that get applied on the Adobe side somewhere?

Similar Messages

  • Remove Prerelease Folio from Multi-Folio Viewer?

    I have a folio and multi-folio viewer made in the prerelease software that is launched and doing well. I've recreated the old folio and a new one to submit with a new viewer. The old folio was recreated in the new DPS system to be able to use the new analytics tools with it.
    In the documentation for prerelease folios it mentions updating prerelease folios with the old software (while it is still available) and that they won't be recognized by the new system. It doesn't mention anything about deleteing them.
    In testing my new viewer I have my first folio release showing up along side the recreated one (I was hoping with the same Product ID's it might override the previous one when published.) Is it possible to delete the prerelease folio that's currently active to repleace it with the new one? Is it better to just stick with the Apple download numbers and go with it being available for download, but not part of the new DPS system?
    Thanks!

    Wes - Unfortunately, there is currently no easy way to replace, or update, a folio created using the prerelease Content Bundler. The program team is working on a solution for an upcoming release. Until then, if the folio is Free instead of Retail, you can use the Content Bundler to delete the old folios, as you suggested, and use the new tools to publish a folio with the same name. But I wouldn't do this if I could avoid it. Your customers who have downloaded the folio will see two identical folios until they delete (archive) the older folio. If your folio is Retail, I recommend holding off on replacing the old folio until a better transition solution is in place.

  • Creating first iPad multi-folio viewer...need ID help

    I am creating a multi-folio viewer that will have monthly issues. I've completed a sample folio and the first two issues.
    I understand to  create a multi-folio viewer, I need one Adobe ID to create all of the folios, and not use the Adobe ID for any other folio production.
    I'm confused on how to name the App Id and Product ID. How are all the issues linked to the sample folio and become available as a purchase and download when each month's issue is ready?
    Thanks!

    You specify the App ID only on the Apple developer site. For best results, use the "reverse DNS" naming convention for the App ID, such as com.publisher.publication. You don't specify the App ID anywhere on the Adobe side.
    Product IDs are required for all published folios, but they're only significant if you're selling the folio. In that case, the Product ID you specify needs to match when you create it in iTunes Connect and publish the folio on the Adobe side. Again, use the reverse DNS approach: com.publisher.publication.issue. Each different folio should have a different Product ID, such as "com.dancer.danceoff.2012october" and "com.dancer.danceoff.2012november." However, folio renditions should share the same Product ID.

  • 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...

  • Help- Urgent- Multi-folio app not showing all languages

    I created a multi-folio app in 6 languages. English the default. English shows up in app store but all the other folios for German, Italian etc don't show up. They are all published and public. I changed my ipad to Italian and I still dont' see Italian as an option. The English showed up. I also submitted the app under all 6 languages when building in App Builder and then created all the language profiles in Itunes connnect.
    What's weird now that I think about it in Adobe Publisher online there is nowhere to specify a language or when I uploaded the folios there was no way to specify a language. So I think the problem is that Itunes doesn't see the other 5 languages? I just can't figure out what is wrong here and there is no documentation on the web or from adobe.
    Please help as my client is going nuts as am I.
    Post here but feel free to email me directly as well as this is urgent.
    [Edited at request of poster]
    Thanks!

    Thanks for responding. I'm trying to follow you. Right now only english shows in the viewer but there are 6 folios. There is a different folio for each language, all published and all apart of the app, same ids etc. So, I guess what you are saying is the only way to get those languages to show up is to use is to use filters?
    My understanding was if I created a multi-folio with 6 folios they will all show up. But right now only one is showing up for English. All the otherlangues don't show up in the viewer. I have no idea why? Shouldn't all the languages show up? I'm been trying to figure out where is the missing setting.
    If you create a multi-folio all folios should show up for everyone regardless of language, right?
    Creating different app for each language is not an option. They spent thousands for the professional account to do this. There must be a setting somewhere I'm missing.
    I just looked up filters. Was I supposed to use that for the other folios?
    Thanks again for helping.

  • Multi folio app problem

    I created a multi folio app, but my folios are not being displayed in my app. What should I do to correct this problem?

    Hi,
    I think I've managed to find you in our system and here is the cause of the problem
    You have created an iOS viewer and an Android viewer each associated with a different Adobe ID, also known as Application ID. However, the only folios you have published appear to be under the DPS Master account.
    The Master account is not meant to be used for publishing, if anything it should only be used the very first time to set up delegate accounts (Admin, App Builder and Application roles).
    Your folios needs to be published respectively under their own Adobe IDs or Application accounts.
    If you have 2 different viewers, the Android folios should be under the Adobe ID you’ve selected for your Android viewer and your iOS folio under the Adobe ID you’ve selected for your iOS viewer.
    The guide Neil provided is a good starting point, I would just add the following link to get a better understanding of all types of accounts:
    http://helpx.adobe.com/digital-publishing-suite/help/account-administration-tool.html
    Hope that helps.

  • Option to Add Built-in Folio to Multi-folio Viewer App

    Dear DPS developers,
    We would like to allow potential customers to preview one issue (folio), but that could bring thousands of downloads a month (our app is #5 in it's category in Canada) and we may lose substantial amount of money on downloads. Sell the ads is not an option for us.
    We can't have a lite version of the viewer either as Apple is rejecting our app - "Binary Rejected.
    Reasons for Rejection: 2.9: Apps that are “beta”, “demo”, “trial”, or “test” versions will be rejected"
    If we can please build our branded viewer the way it's done in Adobe Content Viewer - with access to multi folio content and one build-in folio that is part of the binary code, hence no downloads for it. This will also take signioficant amount of load off Adobe content servers as all the "trial" content will be downloaded from Apple.
    We'll appreciate your feedback.
    Thank you!
    Gennady

    Wes - Unfortunately, there is currently no easy way to replace, or update, a folio created using the prerelease Content Bundler. The program team is working on a solution for an upcoming release. Until then, if the folio is Free instead of Retail, you can use the Content Bundler to delete the old folios, as you suggested, and use the new tools to publish a folio with the same name. But I wouldn't do this if I could avoid it. Your customers who have downloaded the folio will see two identical folios until they delete (archive) the older folio. If your folio is Retail, I recommend holding off on replacing the old folio until a better transition solution is in place.

  • Multi-folio Next Steps?

    I've created a multi-folio viewer, with "sample" material, published the free app and submitted it to Apple. While I wait for Apple's approval, I'm wrapping-up the folios that will follow. but will be for purchase. These folios seem to be working just fine and appearing as a download in Adobe Viewer app on the iPad.
    For some reason, I can't wrap my head around what should be the next steps to publish the folios and submit to Apple. Do I create new certificates, does each new folio have a different bundle ID, what about product IDs? (I am using the same Adobe ID and using a Pro account.) How does everything connect?
    I would appreciate some help getting over this hump.
    Thanks!

    It's hard to tell what in particular is confusing you, so I'll give a quick overview.
    On the Adobe side, you use the Account Admin tool on the Dashboard to assign the application role to the Adobe ID that you use to create and publish your folios. In Viewer Builder, you specify this Adobe ID in the "Title ID" field. Any folio you publish when signed in using this Adobe ID appears in your app's library. It sounds like you understand that part. When you publish a folio, each separate issue should have its own Product ID. Use the format "com.publisher.publication.issue." (If you're creating folio renditions to make the same issue available on different platforms such as iPhone and iPad, use the same Product ID for the different renditions of that issue.)
    On the Apple side, you create one App ID for your app, along with the certificates and provisioning files. If you're selling retail content, you need to use iTunes Connect to create a Product ID for each issue. Again, use the "com.publisher.publication.issue" format. This Product ID should be identical the Product ID you specify on the Adobe side when publishing the folio as Public and Retail. In iTunes Connect, you submit these In App Purchases to Apple for approval. Apple opens the distribution app you submit and inspects the public folios you publish.
    If you have a subscription app, you also need to create a Product ID for each duration. Use the "com.publisher.publication.duration" format. You specify these Product IDs when setting up the subscription app in Viewer Builder.

  • Multi-folio: submitting and approval

    My project has been given the go ahead and we are nearing launch.
    I have read the Adobe Publishing Companion Guide for iPad, searched the forum, and Googled but could not find answers on how a multi-folio app is submitted and approved. I understand that a multi-folio app is an Adobe DPS feature based on a shell/container library app. Does the multi-folio viewer app get submitted to Apple? If so, do I need to do a layout for it (will be using a Professional license)?
    Is there a step-by-step guide that I missed that details the creation and submission of a multi-folio app?
    Thanks,
    Joe

    You need to submit that app to Apple but you also need to make sure there is some content available to be downloaded immediately for review. You can have your first issue published as free and public or perhaps a sample issue.

  • Can you link to other folios in a multi-folio app?

    I want to create an index article in each folio of a multi-folio view app. Can I create links in the index article that will launch another folio or return to the folio in the library?
    Thanks

    Thank you!
    I'm starting to create the index with a link to another folio. The DPS Tips article uses the syntax: [URL Scheme]://v1/folio/[folio name]/[article name]
    What is the "v1/folio/" in the syntax?
    Can the syntax end with "[folio name]" if I just want it to go to the library?

  • Problems updating folios in multi issue viewer

    I created a multi issue viewer app containing two issues. Now I try to update one of these two issues in the DPS Folio Producer Organizer, but the app still shows the old version of the issue.
    I update the issue with the "update"-button and deleted the multi issue viewer and re-installed it on my iPad many times, but the multi issue viewer still shows the old version of the changed issue.
    Finally I deleted the changed issue in the DPS Folio Producer Organizer, but the multi issue viewer still shows the old version of the issue.
    What can I do now?

    I suggest calling enterprise support for this, they should be able to help you figure out what is going on. You can find contact information by logging into http://digitalpublishing.acrobat.com/ and looking in the bottom middle of the page.
    Neil

  • Content Viewer crashes, will my multi-folio app crash as well?

    I am in the process of creating back-issues before our multi-folio app goes live in a couple weeks (my first foray into Adobe DPS). Some articles in my folios are very large in size because of large PNG object state slideshows (about 25 MBs for each article). These articles are now causing Adobe Content Viewer (ACV) to crash, ever since the app was updated to accommodate the v26 versions. I have tried creating identical folios with both v25 and v26 tools, and they both crash when reading the large articles.
    ACV did not crash when reading the exact same folios/articles before the app updated to accommodate the v26 tools. I'm testing on an iPad 1. I will be able to test on an iPad 2 and iPad 3 in a few days. The same type of folios/articles do not cause ACV to crash on android before or after update.
    My question is... does ACV crashing mean my real multi-folio app is guaranteed to crash when it goes live in a few weeks? Or is this a bug in ACV that will not exist in my real multi-folio app?
    Thanks.

    ACV and the custom viewer are the same. If you are seeing problems with ACV you will have the same problems with your custom app. This isn't a bug in the app, it's the app running out of memory because of the complexity of your pages. iPads aren't as powerful as desktops. If you are designing articles with full-page PNG slideshows with multiple states you will wind up with low memory problems. You should rethink your page design to simplify the number of large assets you have.
    Neil

  • Empty Viewer on Test iPad for multi folio iTunes Free Subscription

    Hello,
    I'm trying to test a free subscription, multi folio newsstand app with renditions. However, the viewer opens without any folios - just the subscription tiles. I've triple checked the Apple product IDs, shared secrets and have all of the appropriate certificates. I'm at my wit's end! A few questions:
    Should free subscriptions folios be public/free or retail? I'm reading conflicting things.
    I'm a little unsure of the order in which I should publish folios in the folio producer. Should this step proceed or follow creating the .ipa for testing?
    Does this naming of the actual folios matter, as long as they are the same? I only need the same exact Product ID for iTunes Connect and the App Builder, correct?
    I've noticed that after you enter your shared secret there is a field to enter an iTunes url in the Admin Tool. Which url do we use? Do we enter this after the folio is public?
    Thanks!
    Darin

    Free subscriptions should be Public/Free, not Retail.
    It doesn't matter which order you publish the folios and create the .ipa for testing. When you publish the folios as Free and Public, they should appear in your testing app if (A) you specified the shared secret, (B) published the folios as Public/Free, (C) set up your renditions/folios correctly, and (D) specified the free subscription Product ID created in iTunes Connect in the DPS App Builder.
    When you set up renditions for a subscription app, the Folio Name, Product ID, and Publication Date values need to be the same for all renditions, and different for each set of renditions. Specify the Publication Date values by choosing from the calendar picker.
    Yes, the iTunes URL becomes available when you publish the app.

  • New In-app purchases not showing up in multi-issue Viewer

    Hi all,
    We created a multi-issue Viewer and got that approved together with the first in-app purchase (folio).
    The app is free and downloadable from tehAppstore and the folio can be purchased from within the app as is to be expected.
    Last week however, we've uploaded three new folio's and the have all been approved by Apple last night but they are nowhere to be seen in the app.
    Is there a known delay between approval and visibility in the app?
    Regards, Roel.

    I'm having the same problem. Latest folio, which is 'ready for sale' as an in-app purchase and 'public/retail' in Folio Producer, is not visible on the content viewer. It was only approved by Apple last night - is there a delay?

  • Second folio not appearing in multi folio DPS app – help?

    I'm publishing a second folio in a multi folio DPS app. I have used a new Adobe ID to create the folio. I have published it no digitalpublishing.arcobat.com using PUBIC and FREE.
    This is where I've run into problems, I think. I have tried using a new PRODUCT ID as well as the one from the first folio but neither appeared to have worked.
    QUESTIONS:
    1. What PRODUCT ID do I use?
    2. How long does it take for the new folio to appear on devices?
    3. Does anything have to be submitted to APPLE this time?
    Thanks in advance!

    The term "Product ID" can be confusing because a Product ID can refer to the app itself or to a "product" within the app such as a folio or subscription. In this case, when you publish a folio, the Product ID refers to a product within the app, so you need to distinguish it from other products (folios). That's a long way of telling you to use a different Product ID for each new issue you publish. If you specify the same Product ID for different folios, the viewer will treat them as renditions, and display only one of them. We recommend using the "com.publisher.app.issue" format, such as "com.sportspub.climbingtoday.201406" for the June issue.
    If you publish the second folio as Free and Public using a different Product ID, it should appear right away in your app. (For retail issues, it can take longer for Apple to process the in-app purchase.)

Maybe you are looking for