9 Replies Latest reply on Aug 24, 2013 2:58 AM by szerner
      • 1. Re: Can not debug CS extension with Indesign CC
        Yanwen Level 1

        Right click the project in the Extension Builder, click "Debug As->InDesign CC" in context menu. The InDesign CC will be launched. Open extension to start debugging.

        • 2. Re: Can not debug CS extension with Indesign CC
          ssthakur Level 1

          Hi Yanwen,

          I am using InDesign CC ( trial version) and Flash builder 4.6 with Extension builder 2.0. it is not visible in the context menu. Context menu shows "As Indesign Extension". when we choose this option the it shows Indesign CS 5.5 and CS 6 but not CC version of InDesign.

          • 3. Re: Can not debug CS extension with Indesign CC
            Yanwen Level 1

            You need to use Extension Builder 2.1 to develop extension for CC version of InDesign http://www.adobe.com/products/adobe-extension-builder.html

            • 4. Re: Can not debug CS extension with Indesign CC
              ssthakur Level 1

              Hi Yanwen,

              I did updated Extension builder 2.1. but after updating i can not open manifest.xml file using Bundle Manifest Editor. it throws below error:

              Could not open the editor: An unexpected exception was thrown.

              Please help me.

              • 5. Re: Can not debug CS extension with Indesign CC
                szerner

                Same here, after updating from EB2.0 to EB2.1, I get that same error message, when I try to open my projects manifest.xml using the Bundle Manifest Editor.

                The "Details" view shows

                 

                java.lang.NullPointerException

                    at com.adobe.cside.ui.editors.pages.MainBundlePage.isPointProductSupported(Unknown Source)

                    at com.adobe.cside.ui.editors.pages.MainBundlePage.createTargetAppSection(Unknown Source)

                    at com.adobe.cside.ui.editors.pages.MainBundlePage.createFormContent(Unknown Source)

                    at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152)

                    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

                    at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150)

                    at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:471)

                    at com.adobe.cside.ui.editors.BundleManifestEditor.pageChange(Unknown Source)

                    at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1067)

                    at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:603)

                    at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:352)

                    at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)

                    at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)

                    at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)

                    at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289)

                    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2945)

                    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850)

                    at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842)

                    at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793)

                    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

                    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789)

                    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773)

                    at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:331)

                    at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:179)

                    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

                    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)

                    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)

                    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)

                    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)

                    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)

                    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)

                    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)

                    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

                    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)

                    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

                    at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.ja va:108)

                    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

                    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)

                    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)

                    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)

                    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

                    at java.lang.reflect.Method.invoke(Unknown Source)

                    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)

                    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)

                    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

                • 6. Re: Can not debug CS extension with Indesign CC
                  Carl Sun Level 4

                  I am not Extension Builder expert. You can ask help in Extension Builder forum at http://forums.adobe.com/community/creativesuites/extensionbuilder.

                  • 7. Re: Can not debug CS extension with Indesign CC
                    Yanwen Level 1

                    This is a bug of Extension Builder 2.1. The workaround is to open the manifest.xml at "[ProjectFolder]/.staged-extension/CSXS/manifest.xml" with text editor. Find the element "HostList" like below:

                     

                            <HostList>

                                                  <Host Name="PHXS" Version="13" />

                                                  <Host Name="PHSP" Version="13" />

                                   <Host Name="IDSN" Version="8" />

                                        </HostList>

                     

                    Change the text to

                     

                            <HostList>

                                   <Host Name="PHXS" Version="[13,14.9]" />

                                   <Host Name="PHSP" Version="[13,14.9]" />

                                   <Host Name="IDSN" Version="[8,9.9]" />

                             </HostList>

                     

                     

                    Version number of Photoshop CS6 is 13, the version number for InDesign CS6 is 8. <Host Name="IDSN" Version="8" /> means this extension can be installed for InDesign 8 (CS6) and above. If you change it to <Host Name="IDSN" Version="[8,9.9]" />, the extensoin will only be installed for InDesign 8 (CS6) and InDesign 9 (CC). For other products, do the same changes.

                    • 8. Re: Can not debug CS extension with Indesign CC
                      Yanwen Level 1

                      Please refer to the reply to ssthakur.

                      • 9. Re: Can not debug CS extension with Indesign CC
                        szerner Level 1

                        Will there be any fix for this? It's easy to manually correct some version numer strings, but gets very uncomfortable when you have to configure or add any other options so you need to dive into the manifest.xml docs to be able to do that.

                        For me, the Bundle Manifest Editor was an often used element of Extension Builders GUI.