Prepackaging of HWC app 2.3 in ADT

Hi Experts,
I tried to create a Package in ADT for this I imported the zip file from HybridApp -> Containers -> Android ->
Android_HWC_2.3.0.zip. When I tried to run this .apk file on mobile it is giving me error Sorry "The application Hybrid Web Container (process com.sybase.hwc) has stopped unexpectedly." but I guess that it should run as it a template of HWC. It is running fine when I am running the Android_HWC_2.3.0.zip directly on mobile(without using ADT).
Thanks
Saurabh

Hi All,
It is running fine.
Thanks
Saurabh

Similar Messages

  • IOS app starts with black screen when compiled via ADT (Flex 4.6, AIR3.7)

    I was using Flex 4.6 with AIR 3.1 in Flash Builder 4.6 on Windows 7. I used two build methods: 1) "Export Release Build" in Flash Builder during development and 2) the ADT toolchain on my build server.
    For the ADT method I would create AIR intermediate files using:
    "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\FlashBuilderC.exe" --launcher.suppressErrors -noSplash -application org.eclipse.ant.core.antRunner -data [PATH_TO_SOURCE] -file [PATH_TO_BUILD_XML] [PROJECT_NAME]
    Where my build.xml looks like:
    <?xml version="1.0"?>
    <project default="main">
        <target name="main">
            <fb.exportReleaseBuild project="[PROJECT_NAME]" basefilename="[BASE_FILE_NAME]" verbose="true" destdir="bin-release" />
        </target>
    </project>
    From these intermediate AIR files I would create my APK and IPA files using ADT like so (shown for iOS):
    echo [CERTIFICATE_PASSWORD]|"C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adt" -package -target ipa-test -provisioning-profile [PATH_TO_MOBILE_PROVISIONING_FILE] -storetype PKCS12 -keystore [PATH_TO_DEV_CERTIFICATE] [OUTPUT_PATH] [PATH_TO_IOS_AIRI]
    This procedure produced working iOS and Android apps as well.
    I decided to upgrade AIR to version 3.7. I used the overlay proceedure described here (http://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html). I also updated the namespace in my project to reflect the new AIR version. Using "Export Release Build" in Flash Builder produces working copies of both the iOS and Android apps. Furthermore, the secondary method (used on my build server), produces both APK and IPA files without error. The APK works just fine but the IPA does not. When running the app on an Apple device, it starts up with a black screen and stays this way.
    To summarize:
    Flex 4.6, AIR 3.1: "Export Release Build" and ADT tool chain produce working APK and IPA files.
    Flex 4.6, AIR 3.7 using overlay procedure: "Export Release Build" produces working APK and IPA files, ADT tool chain produces working APK file but IPA file loads black screen on Apple devices.
    More notes:
    I had made a back up of the "4.6.0" directory that holds the Flex and AIR SDK files. If I replace the overlayed Flex 4.6.0 SDK directory with the original (which contains AIR 3.1) and revert the namespace back to 3.1 in my project, everything goes back to normal and I get working apps via both methods described above.
    Edit: I also should note that I've tried many other combinations of Flex and AIR (Flex 4.9.1 from Apache and AIR 3.5/3.6), which all produce the same issue. It seems that the overlay procedure breaks something for ADT with iOS specifically...
    Edit 2: I also noticed that the IPA files output by methods 1 and 2 are slightly different. Opening these with 7-Zip I see that most of the files are the same, but some differ slightly in size (this was due to 'ipa-test' vs 'ipa-ad-hoc'). The odd thing is that in the IPA file that does not work (produced via the ADT method), the SWF file is named "swf3465180827438224920.tmp" while the SWF in the IPA that was created using "Export Release Build is named "[PROJECT_NAME].swf". It almost appears as though ADT fails to rename the temporary SWF file. I also realized that the "Export Release Build" method likely used '-target ipa-ad-hoc', so I tried this in the ADT method with the same result.
    Any thoughts?

    Hello Nimit,
    Thank you for your response. I have tried AIR 3.8 Beta and this did not correct the problem. I downloaded the AIR 3.7 SDK from http://airdownload.adobe.com/air/win/download/latest/AdobeAIRSDK.zip . I have also tried with the new compiler as well, with the same result.
    To keep things simple, I've created a very lightweight example with which I see the issue. I've also been able to remove the Flash Builder step and reproduce the problem with mxmlc and adt only. Since the files are simple, I will just post them here.
    TestApp-app.xml
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/3.7">
        <id>com.company.testapp</id>
        <filename>TestApp</filename>
        <versionNumber>1.0.0</versionNumber>
        <initialWindow>
            <content>TestApp.swf</content>
            <autoOrients>false</autoOrients>
            <fullScreen>true</fullScreen>
            <visible>true</visible>
            <softKeyboardBehavior>none</softKeyboardBehavior>
        </initialWindow>
        <android>
            <colorDepth>16bit</colorDepth>
            <manifestAdditions><![CDATA[
                <manifest android:installLocation="auto">
                    <uses-permission android:name="android.permission.INTERNET"/>
                </manifest>
            ]]></manifestAdditions>
        </android>
        <iPhone>
            <InfoAdditions><![CDATA[
                <key>UIDeviceFamily</key>
                <array>
                    <string>1</string>
                    <string>2</string>
                </array>
            ]]></InfoAdditions>
            <requestedDisplayResolution>high</requestedDisplayResolution>
        </iPhone>
    </application>
    TestApp.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:ViewNavigatorApplication xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" firstView="TestView" applicationDPI="160">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
    </s:ViewNavigatorApplication>
    TestView.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:View xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" title="Test App" >
        <s:VGroup width="100%" height="100%" verticalAlign="middle" horizontalAlign="center" >
            <s:Label text="Hello World!" />
        </s:VGroup>
    </s:View>
    Create the above files in a single directory. Run the following to get a working IPA (method 1):
    > mxmlc +configname=airmobile TestApp.mxml
    > adt -package -target ipa-test -provisioning-profile [PROVISIONING_FILE] -storetype pkcs12 -keystore [CERTIFICATE] TestApp.ipa TestApp-app.xml TestApp.swf
    To reproduce the problem, run the following (method 2):
    > mxmlc +configname=airmobile TestApp.mxml
    > adt -prepare TestApp.airi TestApp-app.xml TestApp.swf
    > adt -package -target ipa-test -provisioning-profile [PROVISIONING_FILE] -storetype pkcs12 -keystore [CERTIFICATE] TestApp.ipa TestApp.airi
    If you unpack the working IPA (from method 1) you will see the file "TestApp.ipa\Payload\TestApp.app\TestApp.swf". However, if you likewise inspect the IPA created via the AIR intermediate method (method 2), you will see the file "TestApp.ipa\Payload\TestApp.app\swf1970057761096800694.tmp" and there will be no "TestApp.swf". In both IPA files, if we inspect "TestApp.ipa\Payload\TestApp.app\Info.plist", we see the snippet:
            <key>CTInitialWindowTitle</key>
            <string>TestApp</string>
            <key>CTInitialWindowContent</key>
            <string>TestApp.swf</string>
            <key>CTMaxSWFMajorVersion</key>
            <string>20</string>
            <key>CFBundleSupportedPlatforms</key>
    So I suspect "TestApp.ipa\Payload\TestApp.app\swf1970057761096800694.tmp" is incorrectly named, cannot be found at runtime and thus displays a black screen.
    This problem is observed when using AIR 3.7. It is not observed when using AIR 3.1.

  • SSO Configuration for HWC applications

    How to Configure SSO for HWC applications? we are configuring HTTP Authentication in SCC for Single SignOn but not been successful. Debugging the issue we found that  MYSAPSSO2 cookie is not being returned.and SSO is not configured in SAP .
    How to enable SSO in HWC apps.
    What are the Other options to ask password in HWC apps( adding additional Security Layers)

    Kunal raman
    You/BASIS admin can check in that particular SAP system.
    Go to Transacation RZ10
    Select Instance Profile as shown in the below diagram
              3
    3 .Click on Display
    4. Then you can see parameter name and its value as below
    Rgrds,
    Jitendra

  • Empty response HWC

    Hi,
    We are working on HWC application with rest webservices MBO approach. Getting empty response in hdc.processDataMessage
    hwc.processDataMessage = function (incomingDataMessageValue) {
      alert(JSON.stringify(incomingDataMessageValue)+"in process data");
        if (incomingDataMessageValue.indexOf("<M>") != 0) {
            alert("An error occurred!  " + incomingDataMessageValue);
        var workflowMessage = new WorkflowMessage(incomingDataMessageValue);
        var values = workflowMessage.getValues();
        alert("values--------"+JSON.stringify(values));
    Below are some queries:
    1. for HWC approach, while generating deploy package, do we need to specify MBO package details?
    2. When we specify, supAdmin/s3pAdmin while creating package, we are getting login error in response for user supAdmin.
    3. If username and password are not specified while creating the package, then it is hitting the service, but empty response is shown?
    Appreciate, if someone guide in debug approach for the same
    Regards,
    Gaurav

    Hi Midhun,
    Thanks for quick reply.
    Are you getting data when you do a preview of MBO ?
    [[]]: Yes. In Preview data is shown properly.
    For HWC application, we followed steps at below scn blog:
    http://scn.sap.com/community/developer-center/mobility-platform/blog/2013/07/18/hwc-application-development-using-hybrid-api-generation-approach
    We are trying creating MBO on sample DB table as well as MBO on rest webservice. In both cases, we are getting empty response.
    I tried adding code specified by you, but mvc is coming as null.
    1. for HWC approach, while generating deploy package, do we need to specify MBO package details?
    To deploy the MBO package right click on the project and select "Deploy Project" and to generate hybrid app from the screen designer right click and choose "Generate Hybrid App".
    [[]]: Do we need to do this step for HWC app?
    Also, while generating deploy package from packaging tool, do we need to specify MBO package?
    Regards,
    Gaurav

  • WFDCN messages for HWC has stopped working in SMP 2.3.5 environment

    HI All,
    We have HWC apps on SMP 2.3.5 server and we just applied PL01 and PL02 to support Android Lollipop devices but after that we have not been able to receive workflow messgaes from backend to Android devices. This was working before the patches were applied.
    We are not able to see even queued messages in SCC or any logs in Gateway system regarding WFDCN without payload.
    Please help
    Regards
    Rahul

    The Android Lollipop support comes was on the client side. It doesn't really make sense why you don't see anything queued on the server if the backend is sending the WFDCN.
    Can you double check if the Android Lollipop devices have push configured properly?
    In SCC, Applications -> Application Connections -> (select Android Lollipop device) -> Properties -> Android Push Notifications.
    What do you see for the Sender ID, Registration ID and Enabled properties?
    Thanks,
    Andrew.

  • App will only install using AIR 1.5.3

    I recently packaged and signed an application using the AIR 1.5.3 SDK. The app will now only install if the user has AIR 1.5.3, and fails with 1.5.2, 1.5.1, etc. The application namespace is AIR 1.5, not 1.5.3.
    This is an application update, though it also fails on a <1.5.3 system without a previous install. I logged the error during app install:
    failed while unpackaging: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="invalid package signature" errorID=5022]
    The certificate used to sign this app has recently expired. Is that the problem?
    This is really frustrating. I intentionally signed the app update BEFORE the cert expired to avoid all this crazy s#%^# about migration signatures, botched publisher ids, requiring users to have AIR 1.5.3 etc (or at least kick it down the road 6 months; AIR 1.5.3 had just come out). Now it looks like all users who try to install this app will need AIR 1.5.3 anyway.
    I suppose that since users need (certain) admin rights to install the app anyway, updating to 1.5.3 won't be a barrier. But it's still an added aggrevation and yet another thing we need to QA. The client won't be happy.
    So is this a bug or a feature? If I signed using the AIR 1.5.2 SDK would the thing still work?

    I understand that I should (need to) use AIR 1.5.3 to update an app _after_ a cert expires.
    However this particular issue should be noted in the documentation, at least after some testing and clarification. Here's the best succinct description of this problem I can think of:
    If you sign an application update with a valid certificate using ADT 1.5.3 and:
    -- your certificate subsequently expires and
    -- it does not define the 1.5.3 namespace then
    you will need to resign your application defining the namespace as AIR 1.5.3 and use the 1.5.3 certificatemigration procedure. Users of your application will be required to update to AIR 1.5.3.
    I haven't yet tested the original application install on a non-1.5.3 system since the certificate expired. However I would _assume_ it still installs, since documentation states that an application signed with a valid certificate (and a timestamp) that subsequently expires will install any time in the future.
    So it seems using ADT 1.5.3 for signing REQUIRES end users to use 1.5.3 because of this problem, since once the cert expires (almost guaranteed to occur during any 12 month period) users with <1.5.3 will see the installation error if the app namespace is not 1.5.3.  This is a fundamental problem since preparing/signing an app with a particular ADT version should not require that version for the end user.
    I'll try to test the original signed app on a <1.5.3 system:
    -- If it works that means this issue should be flagged in the AIR documentation somewhere.
    -- If it fails, that means this post is wrong, and it also means that any AIR app whose cert expires will fail to install.
    So I'll need to re-prepare my app update using the AIR 1.5.3 certificate migration procedure.

  • 6/10/14 - Release - AIR 14 Runtime and SDK

    Today we're pleased to announce that the next version of AIR is available for immediate download.
    This update includes the following fixes and security updates:
    Security update details can be found here: Security Bulletin (APSB14-14)
    New Features:
    Anisotropic Filtering
    This new texture sampling filter can enhance the image quality of textures on surfaces that are at oblique viewing angles.  There are two ways to enable this feature:
    In AGAL, set one of the values – "anisotropic2x", "anisotropic4x", "anisotropic8x", or "anisotropic16x" to the filter option in the sampling instructions.
    Call Context3D::setSamplerStateAt with the 3rd parameter "filter" being one of the values defined in Context3DTextureFilter - "ANISOTROPIC2X", "ANISOTROPIC4X", "ANISOTROPIC8X", or "ANISOTROPIC16X"
    New Stage3D "Standard" Profile
    Developers can now request this high level profile when creating Context3D.  Three new features are available in this profile:
    Multiple render target allows to you to draw geometry to multiple outputs (up to 4) during one drawing
    Floating point texture allows you to create Texture, RectangleTexture and CubeTuxture with the RGBA16F folder.
    AGAL v2 contains these improvements:
    Increased register size
    Partial derivative instructions
    Fragment depth output
    Conditional forward jump
    Intel x86 Android Support
    As announced in our Flash Runtime blog, we're adding support for Intel x86 Android to AIR.  An ADT command line option (-arch) has been added to allow packaging apps with Android x86 support.  Please note that currently only captive runtime packaging is allowed for x86 architecture.  This means all APK targets (apk, apk-debug and apk-captive-runtime) will forcibly be packaged with captive runtime.  Feedback on this approach is encouraged.
    Sample APK packaging command for x86 devices:
    adt -package -target ( apk | apk-captive-runtime ) -arch x86 -storetype pkcs12 -keystore abc.p12 HelloWorld.apk HelloWorld-app.xml HelloWorld.swf
    adt -package -target apk-debug -arch x86 -storetype pkcs12 -keystore abc.p12 HelloWorld.apk HelloWorld-app.xml HelloWorld.swf
    Note that -arch is optional. If not specified, armv7 is assumed.
    Packaging for x86 architecture in Flash Builder:
    Open the debug/run configurations of the project in Flash Builder and click on "Customize launch.." button. Add a new parameter "-arch" with value "x86" and place it before "-storetype". Click "OK" to apply changes.
    Except for RTMPE and DRM, all other features and capabilities are completely functional and supported. Native extensions written for x86 platforms can also be packaged and used by an app for x86 devices. To support this, a new ANE platform 'Android-x86' is now available.
    The following example highlights the usage of the same -
    <extension xmlns="http://ns.adobe.com/air/extension/14.0>
    <id>com.adobe.sample.ane</id>
    <versionNumber>1.0</versionNumber>
    <platforms>
    <platform name="Android-ARM">
    <applicationDeployment>
    <nativeLibrary>sample.jar</nativeLibrary>
    <initializer>com.example.ane.Extension</initializer>
    <finalizer>com.example.ane.Extension</finalizer>
    </applicationDeployment>
    </platform>
    <platform name="Android-x86">
    <applicationDeployment>
    <nativeLibrary>sample.jar</nativeLibrary>
    <initializer>com.example.ane.Extension</initializer>
    <finalizer>com.example.ane.Extension</finalizer>
    </applicationDeployment>
    </platform>
    </platforms>
    </extension>
    New packaging command for ANE:
    adt -package -target ane Sample.ane extension.xml -swc Sample.swc -platform Android-ARM -C Android-ARM/ . -platform Android-x86 -C Android-x86/ .
    Improved Packaging Engine - iOS
    Based on the feedback received from the developer community, tons of improvements and bug fixes have been made in the new packaging engine for iOS.  We encourage developers to report issues to http://bugbase.adobe.com, to ensure that we are able to continue to improve the packager in future releases.
    To enable this feature, please use "-useLegacyAOT no" in the ADT command, before the signing options.  As of now, this feature is not available within Flash Pro but it can still be used with Flash builder by adding the parameter -useLegacyAOT under the "Customize launch" option.
    Here is an example ADT command for compiling an applications using “-useLegacyAOT no":
    adt -package -target ( ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc) -useLegacyAOT no -provisioning-profile -keystore -storetype pkcs12 -storepass xxxx HelloWorld.ipa Helloworld-app.xml HelloWorld.swf
    For more information, please visit Faster compiling with AIR for iOS
    AIR Gamepad
    AIR Gamepad feature enables the app developers to provide a second screen on Android mobile devices for the Flash based browser games. AIR Gamepad API enables Flash based browser apps to connect to a paired Android device running the AIR Runtime app and therefore allowing the Android devices to be used as game controllers or second-screen interfaces.
    Key functionality of this feature:
    Gesture eventsTouch events
    Accelerometer events
    Vibration
    Customize the AIR gamepad screen by applying your own skins
    To learn more about the AIR Gamepad APIs, please refer to the documentation found here.
    To try out the Wand.swc which can be downloaded from here.
    Live samples of AIR Gamepad can be tested using the following links:
    ModelViewer
    HungryHero
    For more information, please visit Android devices with AIR as gamepads
    Fixed Issues:
    [IOS] Resolves an issue introduced in AIR 4.0.0.1390 where DatagramSocket was not receiving packets (3747382)
    [IOS] Values are now set correctly when assigning Vector3D.Y_AXIS to a Vector3D object with -useLegacyAOT=no[Android] Browse file dialog called by FileReference.browse() is correctly displayed on the Nexus 7 and Xoom 4.1.2 (3721032)
    [Android] is ignored for all but one extension when multiple extensions are used (3761458)
    [x86][Android] Workers get terminated even without calling terminate function (3755006)
    [Android] Setting the restrict property on a StageText instance and adding or removing text incorrectly add extra characters. (3749699)
    [iOS] Values are now set correctly when assigning Vector3D.Y_AXIS to a Vector3D object with useLegacyAOT=no (3744595)
    [iOS] ANE doesn't include libraries through platform.xml and throws error on packaging the IPA (3743946)
    [iOS] DatagramSocket not receiving packets on iOS (3742982)
    [iOS] Not able to debug/launch iPad iOS Simulator from Flash Builder. Note: One needs to set a environment variable using the command: launchctl setenv AIR_IOS_SIMULATOR_DEVICE "iPad Retina” Then restart the process and run the application on simulator device of his/her choice. By default iPhone is launched. (3728052)
    [iOS] Not able to debug AIR app in iOS Simulator from Flash Builder when Xcode below 5.x is installed (3727760)
    [iOS7] StageText fontWeight/fontPosture API does not work (3724627)
    [Android] R$Styleable.class goes missing from the final AIR app APK though is included in ANE. (3723876)
    [Android] Starling throws Buffer creation failed. Internal error while createVertexBuffer (3756123)
    [Win] Ctrl+A, Ctrl+C and Ctrl+V now work correctly in StageText fields (3708480)
    Multiple security and stability fixes
    Known Issues:
    [Android] Missing support for XXXHDPI icon on Android 4.4 (3730948)
    [x86][Android] Export Release Build from Flash Builder fails to run app on Android device when -arch parameter is used. (3759405)
    [Android]Captive packaging fails for APK using multiple ANEs, throws OutOfMemoryError. (Workaround: run export _JAVA_OPTIONS='-Xms4096m -Xmx4096m' and then run the packaging command). (3766280)
    [iOS8] A notification dialog is coming after launching any AIR applications. (3771162)
    [Android] ADT Does not pass required heap space to dx.jar (3771118)
    [Android] StageText restrict = "A-Z" not blocked lowercase letters input. (3769801)
    [iOS] Package IPA file with ipa-app-store or ipa-ad-hoc type will case logic judgment with incorrect (3768506)
    [Android] StageText displayAsPassword displays text without mask in landscape on Android (3768443)
    Download Locations:
    AIR 14 runtime for Windows: 14.0.0.110 Runtime Download
    AIR 14 runtime for Macintosh: 14.0.0.110 Runtime Download
    AIR 14 SDK & Compiler for Windows: 14.0.0.110 SDK & Compiler Download
    AIR 14 SDK & Compiler for Macintosh: 14.0.0.110 SDK & Compiler Download
    Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 13 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 13 SDK & Compiler”.
    AIR SDK 14 (Compatible with Flex) for Windows: 14.0.0.110 SDK Windows Download
    AIR SDK 14 (Compatible with Flex) for Macintosh: 14.0.0.110 SDK Macintosh Download
    Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page

    OK! Let's take 7 steps ... an easy answer to a focus problem not a machine problem. (MAC!)
    1.1. Download the Adobe Flash Player file version 14 at Adobe - Install Adobe Flash Player
    1.2 or dowonload the above link: http://download.macromedia.com/pub/flashplayer/current/support/install_flash_player_osx.dm g
    2.1 Double-click the AdobeFlashPlayerInstaller_14_ltrosxd_aaa_aih.dmg in your download folder
    4. Do not double-click the red face (png file) - Installer "Install Adobe Flash Player".
    5. Right click the face to perform a precise selection: Show Package Contents.
    6.1 Select - Contents and double click; Select - Resources and double click; Select - Adobe Flash Player.pkg and double click.
    6.2 Warning!! Select - Contents and double click; Select - Resources and double click; Select - app.bundle and copy it to your internet plugin folder (more work!!)
    7. Select: Continue and complete your installation.
    R. Alexander

  • How to execute two structure type values

    How to execute two structure type values for HWC app in SUP 2,2 ? Added is the screenshot, with the structure and values to be executed. Trying in the preview works fine , but how to process in the application ?

    Thanks Midhun VP i came across result checker , but still checking if there is any work around without result checker. , Will  a HTML view with some Success status work in this scenario .
    Correct me if i am wrong, as per my understanding , Result checkers checks the error code return value from BAPI and shows the respective message.
    If so, what are the Pros and Cons of using Result checker.
    Is it suggested to use Result checker for read only operations applications i,e which does nt involve operations( CUD)

  • AIR 4.0 captive runtime won't run: "requires a version of Adobe AIR" alert

    I'm creating an AIR captive runtime application, and it won't run on a target Windows* machine. It displays the following alert instead:
    This application requires a version of Adobe AIR which cannot be found. Please download the latest version of this runtime from http://www.adobe.com/go/getair, or contact the application author for an updated version.
    How can I package the captive runtime differently so it won't display this message? The application is a pure ActionScript app compiled with the adt binary from the standalone SDK (this is not Flex).
    In addition, I'm disturbed that a captive runtime AIR application pings Adobe in any way. I am seeing occasional pings to an adobe site upon launch of the app (something like airdownload2.adobe.com, if I remember correctly). No I'm not using any service calls in my app at this point in development, it's very simple, and should not be pinging the net at all. Why is this happening? I need to disable this too.
    * Problem occurring only on a particular Windows 7 Home Premium 64-bit machine. Unfortunately, this is the end client's machine so I can't tinker with it.

    Do you have access to the problematic machine? If so, maybe you could try to install Sysinternal's Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb896645
    Run the tool, create filter to see just events containing your app name and try to find in the result any issue... you could also compare the log with same log from not problematic machine or with app made with older SDK which was working.
    That's all what I can do... it's a shame that nobody from Adobe is interested yet... maybe you could also submit a bug.

  • Sap Mobile platform Tutorialst

    Hello,
              I need to consume the sap backend in android,this can be possible by using the "SAP Mobile Platform and SAPR3<>NetWeaverGateway<>SUP-ODP<>RelayServer<>Device".I already registered with the open sap, i have done  the self study for the course SAP mobile Solution Development for Enterprise,so now i got some information on it i need to learn it very depth.
    I have few questions.
         1.Is their any other online training  courses available on sap mobile platform ?
         2.Open Sap will soon start any training courses on sap mobile platform ?
    Thanks in advance sorry for bad english
    Regards,
    Navaneeth prodhutur

    The architecture you given uses Odata exposed from NW gateway and SMP will be an online data proxy. Relay server can be used for more security. To know how to develop android apps in this architecture follow this,SyBooks Online
    Other types of applications that you can develop using SMP include Object API based (as Jitendra mentioned, Developing SAP Android Mobile app from scratch), HWC apps (HWC mobile app development for dummies), apps using third party frameworks (http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01942.0230/doc/pdf/smp_tutorial_hybrid_app_package_devel…) and rest apis (http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01926.0230/doc/pdf/smp_devguide_rest_api_applications.pd…).
    Helpful links,
    http://scn.sap.com/thread/3205550
    http://scn.sap.com/thread/3436603
    http://scn.sap.com/docs/DOC-36056

  • 7/8/2014 - Beta - AIR 14.0.0.143

    Adobe AIR Beta Channel Update
    This beta release provides access to the latest AIR runtime and SDK (with compiler) for Windows, Mac OS, iOS and Android.  You can download the AIR beta here: Download Adobe AIR 14 Beta - Adobe Labs
    Below are some of the key features and benefits of AIR 14.  Please see our release notes for full details.
    New Features:
    Anisotropic Filtering
    This new texture sampling filter can enhance the image quality of textures on surfaces that are at oblique viewing angles.  There are two ways to enable this feature:
    In AGAL, set one of the values – "anisotropic2x", "anisotropic4x", "anisotropic8x", or "anisotropic16x" to the filter option in the sampling instructions.
    Call Context3D::setSamplerStateAt with the 3rd parameter "filter" being one of the values defined in Context3DTextureFilter - "ANISOTROPIC2X", "ANISOTROPIC4X", "ANISOTROPIC8X", or "ANISOTROPIC16X"
    New Stage3D "Standard" Profile
    Developers can now request this high level profile when creating Context3D.  Three new features are available in this profile:
    Multiple render target allows to you to draw geometry to multiple outputs (up to 4) during one drawing
    Floating point texture allows you to create Texture, RectangleTexture and CubeTuxture with the RGBA16F folder.
    AGAL v2 contains these improvements:
    Increased register size
    Partial derivative instructions
    Fragment depth output
    Conditional forward jump
    Intel x86 Android Support
    As announced in our Flash Runtime blog, we're adding support for Intel x86 Android to AIR.  An ADT command line option (-arch) has been added to allow packaging apps with Android x86 support. Please note that both shared and captive packaging is now allowed for x86 architecture. More information can be found in this blog post: http://blogs.adobe.com/airodynamics/2014/06/26/versioning-of-multiple-apks-for-android/
    Sample APK packaging command for x86 devices:
    adt -package -target ( apk | apk-captive-runtime ) -arch x86 -storetype pkcs12 -keystore abc.p12
    HelloWorld.apk HelloWorld-app.xml HelloWorld.swf
    adt -package -target apk-debug <debug options> -arch x86 -storetype pkcs12 -keystore abc.p12 HelloWorld.apk
    HelloWorld-app.xml HelloWorld.swf
    Note that -arch is optional. If not specified, armv7 is assumed.
    Packaging for x86 architecture in Flash Builder:
    Open the debug/run configurations of the project in Flash Builder and click on "Customize launch.." button. Add new parameter "-arch" with value
    "x86" and place it before "-storetype". Click "OK" to apply changes.  Except RTMPE and DRM, all other features and capabilities are completely functional and supported. Native extensions written for the x86 platform can also be packaged and used by an app for an x86 devices. To support this, a new ANE platform 'Android-x86' is now available. The following
    example highlights the usage of the same -
    <extension xmlns="http://ns.adobe.com/air/extension/14.0">
    <id>com.adobe.sample.ane</id>
    <versionNumber>1.0</versionNumber>
    <platforms>
    <platform name="Android-ARM">
    <applicationDeployment>
    <nativeLibrary>sample.jar</nativeLibrary>
    <initializer>com.example.ane.Extension</initializer>
    <finalizer>com.example.ane.Extension</finalizer>
    </applicationDeployment>
    </platform>
    <platform name=“Android-x86">
    <applicationDeployment>
    <nativeLibrary>sample.jar</nativeLibrary>
    <initializer>com.example.ane.Extension</initializer>
    <finalizer>com.example.ane.Extension</finalizer>
    </applicationDeployment>
    </platform>
    </extension>
    New packaging command for ANE:
    adt -package -target ane Sample.ane extension.xml -swc Sample.swc -platform Android-ARM -C Android-ARM/ . -platform Android-x86 -C
    Android-x86/ .
    Improved Packaging Engine - iOS
    Based on the feedback received from the developer community, tons of improvements and bug fixes have been made in the new packaging engine for iOS.  We encourage developers to report issues to http://bugbase.adobe.com, to ensure that we are able to continue to improve the packager in future releases.
    To enable this feature, please use "-useLegacyAOT no" in the ADT command, before the signing options.  As of now, this feature is not available within Flash Pro but it can still be used with Flash builder by adding the parameter -useLegacyAOT under the "Customize launch" option.
    Here is an example ADT command for compiling an applications using “-useLegacyAOT no":
    adt -package -target ( ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc) -useLegacyAOT no -provisioning-profile -keystore -storetype pkcs12 -storepass xxxx HelloWorld.ipa Helloworld-app.xml HelloWorld.swf
    For more information, please visit Faster compiling with AIR for iOS
    AIR Gamepad
    The AIR Gamepad feature enables an app developer to provide a second screen on Android mobile devices for the Flash based browser games. AIR Gamepad API enables Flash based browser apps to connect to a paired Android device running the AIR Runtime app and therefore allowing the Android devices to be used as game controllers or second-screen interfaces.
    Key functionality of this feature:
    Gesture eventsTouch events
    Accelerometer events
    Vibration
    Customize the AIR gamepad screen by applying your own skins
    To learn more about the AIR Gamepad APIs, please refer to the documentation found here.
    To try out the Wand.swc which can be downloaded from here.
    Live samples of AIR Gamepad can be tested using the following links:
    ModelViewer
    HungryHero
    Known Issues:
    [iOS 8] A notification dialog is coming after launching any AIR applications. (3771162)
    Fixed Issues:
    3778961: StageVideo with camera doesn't work properly in AIR and Flash Player 14
    About the Beta Channel
    If you would like real-time notification for announcements related to the AIR Beta Channel please follow the Flash Runtime Announcements forums by choosing "Follow this forum" from the right-hand menu on the Forums page.
    You can find instructions for getting started with this release here: AIR Labs Page

    Steve
    I have same problem with apple Developer Id Application certificate (downloaded from apple), got past the chain error message by including intermediate and root certificates when I exported from keychain, but got the package error referenced here. Also when I sign on windows machine with my code signing certificate (selecting windows installer) all publishes ok, but the certificate is not attached, says 'unknown developer' when I down load and try and run installer on windows machine. I sent the exe to Comodo (the guys I got the code signing certificate from) and they say the exe is not signed.
    Finally I get 'The digital certificate is invalid'  error when I try and use 'Developer Id Installer' certificate (downloaded from apple).
    I think there must be several problems here with Air SDK.
    Stopping me from publishing and I have a very upset Customer. Can someone from Adobe please advise asap.

  • SMP 2.3 MBO approach -Mapping of input fields in custom.js

    Hi,
    Please help me.I just want do to mapping of some input fields and personlization keys through  custom.js on click of menu item.
    Thanks
    Ashish Baghel

    Check the below option:
    option 1:
    Create a new editbox in the same screen where the list is (as you did).
    Map the input data binding with key of the listview.
    Later hide the listview using the code below
    //Ios
    Use this in custombeforeshowscreen() or customBeforeWorkflowLoad()
    $('div[id="LoginScreenDiv"] #LoginScreenDivLogin').attr('style','display:none');
    This code from workflow_jQueryMobileLookAndFeel.html page.
    <div data-role="page" data-theme='a' id="LoginScreenDiv" sup_screen_title="Login" style="; background-image: url('Generated%20Workflow/SO_4/html/images/test.jpg'); background-repeat: repeat" sup_menuitems="Cancel Screen,Cancel Screen,Login,Login" sup_okaction="doCancelAction()">
          <div data-role="header" data-position="inline">
           <a href="javascript:void(0)" data-icon="arrow-l" id="LoginScreenDivCancel_Screen" name="Cancel Screen" onclick="menuItemCallbackLoginCancel_Screen();"> Cancel Screen</a>
           <h1>Login</h1>
           <a href="javascript:void(0)" id="LoginScreenDivLogin" name="Login" onclick="menuItemCallbackLoginLogin();"> Login</a>
    </div>
    option 2:
    Customize the screen with the data a HTMLView. Ex, Developing HWC app with Customized List
    In the given example the data is shown in a listview instead show it in a <p> or <h> tags.
    Midhun VP

  • Send data from one phone to another via IR port

    Hi
    I am trying to implement a J2ME program over a Nokia 3200 to exchange data with another phone via IR. Is there any API to do it? Any suggestions, pls.

    So you want to do a online request while navigating to second screen using the employee ID selected? If yes follow this,
    Assume we have 2 screens, screen1 and screen2. Create a editbox in screen 2 and map the key of the editbox with key of employee ID.
    Drag and drop a a HTMLView from control to screen2. and in the properties>default field provide this : <div id = "HTMLList"></div>
    Create a custom action in screen2,ex.GetDetail. The online request of this custom action will do the second call to SAP with employee ID as input. So map the employee ID present in the screen2 as input of this request and give the success screen as screen2 (same screen). A method will be created for this action, call that method inside function customBeforeShowScreen:
    if(screenToShow==="Screen2") {
             menuItemCallbackScreen2GetDetails();
      return true;
         4. For the HTML View write code to show the data as mentioned in the blog, Developing HWC app with Customized List
    Midhun VP

  • Language Conversion issue of HWC SUP APP

    Hello Experts
    Can any one have idea for conversion the hwc sup App from English to other language(French) which was built in SUP2.1.3?
    Thanks in advanced for your suggestion.
    Thanks
    Anil

    Have you restarted the application or device after you changed the device language to French?  The HWC will pick up the current language when it is started.  If you change the device language when the application is already launched, it is not going to pick it up until the next time it is restarted.
    The current device language is passed into your application on the query string with the lang parameter.  You can display the value of this parameter in an alert to double check the app has the language that you think should be displayed. 
    URL Parameters
    Then make sure your localized application has a Locale Properties file that matches what the device is showing for lang.
    Localizing a Hybrid App Package
    Thanks,
    Andrew.

  • How to compile an .air app from the ADT command line?

    Hi,
    I would like to compile an .air app from the ADT command line.
    Does anybody have an example?
    I don't know how to add the AIR SDK path and a folder to it.
    Is there a generator for the command line availabble?
    Thanks

    Correction: it seems that Applescripts and some similar scripts can be called from the command line using "osascript scriptname". I don't speak automator but you might like to try it. osascript seems to come with severe limitations though, for instance it doesn't allow user interaction such as dialogue boxes.

Maybe you are looking for