Folio focus error

Similar Questions

• Migration folio account error

  When I try to access my account of folio Viewer Adobe DPS/content in the new Adobe web portal post, I received the error: "ERROR: no content was found in the account provided.» I can still see my content on the Viewer on a device application. Is there a bug or a fix for this?

  

  Is the DPS account that you use to connect has an Application role? The source account must have an Application role.

  If is an account of the Application, does it include slips that are published in the form of Public? There should be at least one.

• V32 App Bug critical: Folio download error!

  None of the folios will download in our 32.0.2 iOS8 app and our customers are very angry. This has happened for several days now without any difficulty. The State of the Adobe page shows still green, even if it is a critical distribution error that happens to a lot of customers DPS. A customer told us that the app shows 3G of space on its iPad since a previous downloaded question! Please fix this soon Adobe!

  See the download iPad folio issue "can not connect to Server".

  Neil

• Folio Preview error with the Vertical Articles

  I'm trying to build a basic folio.

  I get an error noticed when I try to preview it on an iPad.

  After several sessions of trials and errors, I created a new brand folio, allegedly with guidance a portrait and landscape.

  If I insert a section of landscape, it works as expected.

  If I load a portrait article it throws the preview error dreaded.

  Here are the details:

  • InDesign CS6 (8.0.1)
  • Mac OSX (10.8.5)
  • Folio dual orientation, containing:
  • A single, single article page (standard 1024 x 768, in vertical)

  I have rebuilt the folio as the article page probably 6 times in the last three days trying to isolate this problem.

  Apparently, Miss me something.

  Someone at - it recommendations?

  

  If you preview of Folio Builder Panel you * must * have a portrait and a landscape of article of the folio version when you have selected the double direction otherwise, you will get this error. If you preview the Folio overlays Panel, it will be just a glimpse of the open document and everything that is on your folio is not serious.

  After typing this... don't do a folio dual orientation. It doubles your time of design, almost double the size of your folio and does not provide any benefit to your reader. To do this, choose a direction and design.

  Neil

• Folio Builder - error has occurred trying to connect.

  Hello
  I'm working on a presentation of the Tablet and everytime I try to log in my folio Builder I get this message:

  «An error has occurred trying to connect to the Panel Folio Builder.»

  I tried to login several times today, but I get the same message. It was working fine last week. Is anyone else getting this same message? Is there something wrong with the servers of Adobe at the moment?

  Try to connect to https://digitalpublishing.acrobat.com and see if you are prompted for a terms of use. Then try again.

  If this does not work, see this paper:

  ishing.html http://helpx.adobe.com/Digital-Publishing-Suite/KB/Troubleshoot-Folio-Builder-Digital-publ

• May 1, Folio producer error

  Hello

  Today I connect and cannot update the Folios. I get the following text will appear in the web interface.

  An error has occurred when saving your changes.

  A newer version of the Folio Builder is available for download. Update Folio Builder to the latest version here.

  Not really sure why I need to update whatever it is, it comes to the web interface but I follow the link anyway and download the folio generator is available

  Here goes to http://www.Adobe.com/support/downloads/collection.jsp?collID=4 & Platform = Win

  I don't then go to http://www.Adobe.com/support/downloads/detail.jsp?ftpID=5155

  and download the same version I already have. And so, still get the error message.

  Tried to refresh the cache in chrome and IE.

  If anyone can offer advice, it would be welcome.

  The tools are being updated, which is the likely cause of this error. Please try again in an hour or two.

• Folio upgrade: error #3115table 'folioFolderCache' already exists

  I just upgraded the Folio Builder with a version for Indesign CS5.

  It worked well on initial installation for a few hours until what I closed Indesign. And when I opened Indesign I started getting this error message:

  An error has occurred when saving your changes to the local cache [error #3115table 'folioFolderCache' already exists]

  I can't use Folio Builder. Anyone know how to operate again?

  : S

  Thanks in advance.

  B

  Hello

  Take a look at this thread: http://forums.adobe.com/message/4265514#4265514

  Find out if the proposed solution has helped solve the problem.

• A Folio build error

  Hello everyone,

  When generating a Folio in InDesign CS6 I get the message: "content generation error. [Error: could not find the resources of one or several layers.] Check the resources used are available on the disc, then apdate article].

  The preliminary check shows a green light, that all links are connected.

  I started this project with a trial version of InDesign CS6 in English, then my company gave me a copy recorded in Italian. This could be the reason for the problem, or there is something else?

  Try and rename using the format suggested, ending with _play.png/_pause.png

  so use audio_controls_001_Pause.png instead of audio_controls_Pause_001.png

• Folio export error to the producer of folio

  Hello

  I want to try to create a unique edition of the app Builder application.

  I get this when you try to export a folio of the folio producer:

  

  tried several times with different folios in different app account on mac and PC and still the same (about 10 shots each, I've read before that some did try several times)

  any idea?

  Can someone look into your account and perhaps check your assets so you should call support with your Application ID

• folio preview error

  Invalid value for parameter 'portraitDocument' of the method "exportMiniFolio". Expected, but received document Store/overlaypreview.folio /Local. /Users/natala/Library/Preferences/StageManager.BD092818F67280F4B42B04877600987F0111B594.1

  someone knows how to solve? pls!

  Try trashing your InDesign preferences.

  Bob

• Error downloading folio for iPad via Content Viewer

  Hello

  I'm having issues, get the folio to download on the Adobe Content Viewer for iPad app... whenever I get this message "folio download error. Please try again later. »

  I built a folio of single-app:

  1024 x 768

  Version of the Viewer: 20

  Orientation: Horizontal

  PDF format

  Adobe InDesign CS6 with the latest tools and folio Builder

  The folio consists of a single article with a page that contains two video files (two vignettes that play in full screen when it is turned on)

  10.8.2 OSX

  I have an iPad 2 and iPad 3rd generation I have Adobe Content viewer on iOS 6 (latest version)

  I tried to remove the application viewer content and re - download a new version, I tried to completely rebuild the folio from scratch, I also created a new username Adobe with an expense account to try the folio with... and each time it downloads fine without error... but refuses to download on the iPad.

  Can someone tell me what I am doing wrong or what I should try?

  Doesn't sound that you do something wrong at all. It could be due to performance issues on our servers that create problems to download large files. Here are a few things you can try:

  • If the folio is not already published, republish it as private. Downloads of published folios are often faster.
  • Try to create two sections each containing a video. Download plus two small files is generally better than downloading a large file.

  If it still does not respond, you can share the folio with [email protected] and I'll be happy to take a look.

• Ghost files - cannot delete Trash: error 50

  Hello

  I have trouble to delete some files from Ghost that appeared in my garbage can:

  

  By emptying the Recycle Bin, 50 pops up an error: "the operation cannot be completed because an unexpected error occurred (error code - 50)."

  I looked at lots of different topics already, nothing works. I place them in a folder and because of the different actions on the file (because the files always come with an error (cannot rename (focus error), too long to be moved, etc. file name)):

  I have so far:

  • Tried to delete the files with
    • iTrash
    • DaisyDisk
  • Repaired "Macintosh HD" with my account disk utility.
  • Fixed "Macintosh HD" using disk utility from the recovery partition (Cmd - R to start)
  • Check the file permissions in the file properties
  • Because disk utility is not the "Fix permissions" button (in El Capitan), I fixed the permissions with DiskWarrior.
  • Tried to move the file to a disk and then format the drive, but OS X Copy the folder instead of moving.
  • By using all the methods of the command prompt, I found on other messages of the forum (I don't want to navigate through my history to list them).

  Yet the 50 error is still popping! Currently the thought of another workaround solution...

  I know that the following would allow to settle, but I'd rather not have to do:

  • Reinstall from backup Time Machine prior
  • Create a new account and delete my old account.

  Someone at - it a technique to solve this problem?

  Thank you

  James

  OK, I found a nice workaround with iCloud drive and an iOS device.

  Here's what I did:

  1. Move the folder containing Ghost files to my iCloud Drive in the Finder and wait 30 seconds to display in the player to iCloud on my iOS device application 9.
  2. Remove my iCloud drive to iCloud preferences window in Mac system preferences
  3. Delete the iCloud drive folder using the iOS app
  4. Reconnect to iCloud Drive on my Mac.

  Good riddance!

• The function ' copy to ' in folio Builder... does not work

  So it would appear that the function "copy to" in folio Builder... does not work,... it DOES well, but when you try and publish the folio, it errors saying there is an article in your folio is the bad resolution for the folio...

  What a bore... ! I thought I'd hit goldust to my retina display folio. :-(

  A strange thing about the feature copy, it's that you can use to add any item to any folio. For example, you can add an article to the iPhone to an iPad folio, but you will end up having to delete this article if you want to preview or publish. In your case, it seems that you've added an article from 1024 x 768 to a folio of 2048 x 1536.

  Using the function "Add" is not an effective method for creating applications. I recommend that you configure your files to import. See the following article:

  http://helpx.Adobe.com/Digital-Publishing-Suite/help/structuring-folders-imported-articles .html

• Inherited in Kindle Viewer handling PDF format sheets

  I work with a client to publish a magazine on Kindle Fire. The magazine, a bimonthly, is available on the iPad since over a year now. All the slips that we have produced for the iPad are in PDF format. (Which turned out to be a good decision, as they will display well on the new iPad.)

  We will produce a rendering of 1024 x 600 for the Kindle goes forward. However, all folios inherited appear in the library of the Kindle reader and are not legible. The player displays an error when you try to open one of the old folios. ("This folio contains one or more PDF chimneys that are not yet supported... »)

  I want to prevent some frustration for our readers here, but we do not have the budget or time to rebuild all folios inherited as documents of 1024 x 600.

  The Kindle displays properly folios focused on the 1024 x 768 PNG by adding bars at the top and bottom of the screen. Is not ideal, but sufficient. If we were to shave a few pixels - say 4 or 6 - width legacy folios and rebuild them as folios PNG-based, the difference would be enough for the Kindle to recognize these "renditions" and load it instead of the full-size folios? And the iPad would ignore the slightly narrower folios? That would allow us to solve the problem without having to redraw the value of a year of magazines.

  Thanks to Adobe and Amazon to work with the Kindle viewer questions. Can't wait to see our publications on both platforms soon.

  SB

  If you configure the "renditions" (same sheet name, different values of the size) between folios, it should work. Try to shave a pixel and creating a 1024 x 767 folio and the source of the documents. It certainly will not be displayed on the iPad (viewers iPads folios only 4:3 aspect ratio display), and if you set up "renditions" correctly, the folio of 1024 x 768 will not be displayed on Android.

• NullPointerException: moveFocusToFieldWithInput

  I'm running in an intermittent Ref null exception using the Simulator 6.0.0.246 & 6.0.0.337 9800 Torch generic.

  It happens that I drag in the space of a VerticalFieldManager which contains 2 fields or more active (for example, a BasicEditField and a PasswordEditField). For me, it looks like this method, moveFocustToFieldWithInput try to pick the closest focusable field where the user is drag and give the focus to this field.

  Here's the exception stack trace (code RIM all):

  Java Exception data
   NullPointerException
   No detail message
   net_rim_cldc-13(4C94D16C)
   Manager
   moveFocusToFieldWithInput
   0x8D0A
   net_rim_cldc-14(4C94D16C)
   Screen
   moveFocusToFieldWithInput
   0x294F
   net_rim_cldc-14(4C94D16C)
   Screen
   dispatchTouchEvent
   0x2BF4
   net_rim_cldc-15(4C94D16C)
   UiEngineImpl
   processMessage
   0x6BC8
   net_rim_cldc-9(4C94D16C)
   Application
  
   0x2CBE
   net_rim_cldc-9(4C94D16C)
   Application
   processNextMessage
   0x1BEA
   net_rim_cldc-9(4C94D16C)
   Application
   enterEventDispatcher
   0x1B0F
  

  It is quite easy to reproduce on the Simulator, but I can't reproduce it on a real device.

  I was wondering:

  1A anyone had this problem before and if so what did they do to solve

  2 do you have any suggestions on how to intercept this exception

  3 do you have any ideas on what is the source of the problem

  Thanks in advance.

  Thanks for your reply Mark, thank you for taking a look at this.

  What follows is an application of 1 screen which reproduce this bug but also identifies what can be done to hide the bug (concealment however is hardly a real solution).

  There are comments that describe how to reproduce the bug, but here they are outside of the code:

  1. Run the following application on a Torch 9800 Simulator (I tried two 6.0.0.246 and 6.0.0.337)
  2. Ensure the focus is in the area of the editor 'user_name '.
  3. Tap the screen just below the label of "Password".
     • touch under the password field properly sets focus to the field
     • ensure that you tap outside the limits of the label (which has an aqua background
     • ensure that you hit the limits of the RowManager (identified by color biscuite)

  You can also reproduce this bug by:

  1. Run the following application on a Torch 9800 Simulator (I tried two 6.0.0.246 and 6.0.0.337)
  2. Ensure the focus is in the area of the editor "Password."
  3. Tap the screen just below the label "Username".
     • area affecting as the user properly sets focus the field
     • ensure that you tap outside the limits of the label (which has an aqua background color)
     • ensure that you hit the limits of the RowManager (identified by color biscuite)

  Notes:
  In this case, this bug can be 'hidden' by ensuring that the RowManager.getPreferredHeight returns the maximum value of the field's highest - by doing this that you make it impossible for the user to click below the label

  package ca.focuserrorapp;
  
  import net.rim.device.api.system.Display;
  import net.rim.device.api.ui.Color;
  import net.rim.device.api.ui.Field;
  import net.rim.device.api.ui.Manager;
  import net.rim.device.api.ui.UiApplication;
  import net.rim.device.api.ui.XYEdges;
  import net.rim.device.api.ui.component.BasicEditField;
  import net.rim.device.api.ui.component.LabelField;
  import net.rim.device.api.ui.component.PasswordEditField;
  import net.rim.device.api.ui.container.MainScreen;
  import net.rim.device.api.ui.container.VerticalFieldManager;
  import net.rim.device.api.ui.decor.BackgroundFactory;
  
  /*
   * Steps to reproduce the bug described here: http://supportforums.blackberry.com/t5/Java-Development/NullPointerException-moveFocusToFieldWithInp...
   *
   *  1. Launch the following application on a Torch 9800 simulator (I've tried both 6.0.0.246 and 6.0.0.337)
   *  2. Ensure focus is in the 'Username' editor field
   *  3. Touch the screen just below the 'Password' label
   *     - touching below the password field correctly assigns focus to the field
   *     - ensure you touch outside the bounds of the label (which has an aqua background color)
   *     - ensure you touch inside the bounds of the RowManager (identified by the bisque color)
   *
   *  You can also reproduce this bug by:
   *  1. Launch the following application on a Torch 9800 simulator (I've tried both 6.0.0.246 and 6.0.0.337)
   *  2. Ensure focus is in the 'Password' editor field
   *  3. Touch the screen just below the 'Username' label
   *     - touching below the username field correctly assigns focus to the field
   *     - ensure you touch outside the bounds of the label (which has an aqua background color)
   *     - ensure you touch inside the bounds of the RowManager (identified by the bisque color)
   *
   * Notes:
   *
   * In this case, this bug can be "hidden" by ensuring the RowManager.getPreferredHeight returns the max
   * value of it's tallest field - by doing this you make it impossible for the user to click below the label
   *
   */
  
  public class FocusErrorApp extends UiApplication {
    public static void main( String[] args ) {
  
      FocusErrorApp app = new FocusErrorApp();
      app.enterEventDispatcher();
    }
  
    public FocusErrorApp() {
  
      this.pushScreen(new TestScreen());
    }
  
    static final class TestScreen extends MainScreen {
      public TestScreen() {
  
        super();
  
        this.setTitle("Focus error test application");
  
        this.initLayout();
      }
  
      protected void initLayout() {
  
        int containerWidth = 250;
        int containerHMargin = (Display.getWidth() - containerWidth) / 2;
        VerticalFieldManager uxLoginContainer = new VerticalFieldManager();
        uxLoginContainer.setMargin(new XYEdges(0, containerHMargin, 0, containerHMargin));
  
        BasicEditField uxUsername = new BasicEditField("", "", 50, BasicEditField.USE_ALL_WIDTH
            | BasicEditField.NO_NEWLINE | BasicEditField.NO_LEARNING | BasicEditField.NON_SPELLCHECKABLE
            | BasicEditField.NO_COMPLEX_INPUT);
  
        PasswordEditField uxPassword = new PasswordEditField("", "", 50, PasswordEditField.USE_ALL_WIDTH);
  
        uxLoginContainer.add(new RowManager("Username", uxUsername));
        uxLoginContainer.add(new RowManager("Password", uxPassword));
  
        this.add(uxLoginContainer);
      }
  
      private class RowManager extends Manager {
  
        private final LabelField uxLabel;
        private final Field uxEditor;
  
        public RowManager( String label, Field editor ) {
  
          super(Manager.USE_ALL_WIDTH);
          this.uxLabel = new LabelField(label);
          this.uxLabel.setBackground(BackgroundFactory.createSolidBackground(Color.AQUA));
          this.uxEditor = editor;
          this.uxEditor.setBackground(BackgroundFactory.createSolidBackground(Color.GREENYELLOW));
  
          this.setBackground(BackgroundFactory.createSolidBackground(Color.BISQUE));
  
          this.add(this.uxLabel);
          this.add(this.uxEditor);
        }
  
        public int getPreferredWidth() {
  
          return Display.getWidth();
        }
  
        public int getPreferredHeight() {
  
          return 50;//Math.max(this.uxLabel.getPreferredHeight(), this.uxEditor.getPreferredHeight());
        }
  
        protected void sublayout( int arg0, int arg1 ) {
  
          this.setPositionChild(this.uxLabel, 0, 0);
          this.layoutChild(this.uxLabel, 150, this.uxLabel.getPreferredHeight());
  
          this.setPositionChild(this.uxEditor, 155, 0);
          this.layoutChild(this.uxEditor, 150, this.uxEditor.getPreferredHeight());
  
          super.setExtent(this.getPreferredWidth(), this.getPreferredHeight());
        }
      }
    }
  }