After I migrated my project Worklight from version 6.0 to 6.1, the following error is occurring when trying to deploy the application:
[2013-12-19 11:37:02] FWLST1040E: android build failed: Cannot
overwrite template file
'C:\workspaces\worklight\CISSMartTax\apps\CISSMartTax\android\native\native.iml'
Unfortunately this currently works for me.
In Worklight 6.0.0.1 I've created a new Worklight project and application with the Android environment, built and deployed it
I then exported the Worklight project as a .zip file
In Worklight 6.1.0 I've imported the above .zipped project, built and deployed it
Ran the generated Android project in the Android emulator
This was with a blank new app; it's possible yours is more intricate than that.
Suggestions:
Delete the native folder and re-build and deploy.
Make sure to back-up any native Java classes and other artifacts you may have previously added to the native folder.
Provide your Worklight project (the original from 6.0.0.x) in a Dropbox download link for analysis...
Related
i have created the sample app 0n mobilefirst 7.1 with mac 10.12.5 java 1.8 eclipse mars, once i have created project added the android and ios environment after done build all environment ,ideally it should create separate android folder for that but its not creating any separate android folder , please any solution really appreciated
The most likely cause of the issue is missing "Android Developer Tools" Plugin in your Eclipse. This is required to create the Android native project, when you add Android environment.
Verify its installation.
I am working on hybrid Apps over IBM Mobile First Foundation on eclipse,I want to build an android app of the project, but when i configure the android SDK location and click on apply, nothing happens
Help!
The question is not clear enough... what are you applying? where? are you getting any errors, if yes, what are they?
When using MobileFirst Studio in Eclipse, the Android project can be generated in two ways.
By using the Google ADT tools.
Install the Eclipse plug-in and re-build the project by right-clicking the application folder and selecting Run As > Run on MobileFirst Development Server
By providing the path to Android Studio.
First install Android Studio and then, in Eclipse, navigate to File > Preferences > MobileFirst. Provide the path to the folder containing the executable. For example in Mac OS X that would be /Applications.
Then right-click on the Android environment folder and select Run As > Android Studio project.
Note: be sure not to convert the project to Gradle structure - this is currently not supported.
FWLSE3210W: Environment: android of application BBQ version 1.0 has
been deployed with a different version of the native MobileFirst SDK.
Direct updates will no longer be available for existing clients with
other versions of the MobileFirst SDK. To continue to use direct
updates, increment the app version, publish it to the public app
store, deploy to the server, and (optionally) block/notify older
versions of the app to enforce customers to upgrade to the new version
from the app store.
I am seeing the above warning again and again. And it doesnt seem to be related to the version difference between my worklight studio and worklight server.
I have created a MobileFirst Project in MobileFirst 6.3.
I have a remote MobileFirst 6.3 server.
When I deploy the iphone wlapp file first through the worklight console it goes through successfully but when I deploy the android wlapp file of the same app, it shows me the above warning and similar thing happens when I upload the android wlapp file first no issue but when iphone wlapp file is uploaded it shows the warning. Could someone tell me what this warning really is?
This is a false-positive warning message that you can safely ignore.
If you'd like it gone you can also download the latest MobileFirst Platform Foundation 6.3 iFix from IBM Fix Central where it has been fixed.
Has anyone tried the "Android - Adding native functionality to Hybrid Application using Apache Cordova plug-in" feature in v6.2 ?
I'm trying to use a 3rd party library on the client side and wanted to understand where to put the plug-in java class in the project. The documentation shows a java package (src) structure whereas the best I can find is normal folders in the android native folder.
Thanks.
The reason you see these as "regular" folders is likely because you are look at the Worklight project rather than the generated Android project.
Worklight project\apps\your_app\android\native\ ... will look as folders because they are indeed just folders.
Once you build your Worklight application (containing an Android environment), an Android project will be generated. In it, you will see the folders as packages, etc.
A Worklight project and application structure is explained in earlier training modules:
Creating your first Hybrid Worklight application
Previewing your application on Android
So, you should place your Java Class file in Worklight project\apps\your_app\android\native\src\com\package_name\ ...
Note about Cordova plug-ins in Worklight: depending on the plug-in this may not be possible to use as some plug-ins require using the Cordova plugman, which is not yet supported in Worklight.
My environment :
Eclipse sdk 3.7.2
Worklight pluin 5.0.5
Android sdk 2.2
First I tried a simple Hello World, everything works fine, android native project was created and I see the corresponding apk file was generated after a build and deploy.
Next I imported a sample project, successfully got it run on the test (localhost) server, able to see the expected result on the android Mobile Browser Simulator but the problem now is I am not seeing the corresponding android apk file got generated (the android native project was created). No errors on the logs, Any idea what could be the problem? How one debug such a problem.
APK will be generated under \bin\ folder once you run your app for the first time.
Connect your Android device to dev machine via USB cable (assuming you got Android SDK etc installed), right click on Android project and do Run as->Android app.
The app will be installed and started on Android device. APK will be generated in \bin folder.
In general, you don't need the device, same thing can be done with emulator.
You can also do an export on the android application project. This is what you would do if you are looking at doing some key signing. This is the way you would want to export it if you are uploading to Google play or an enterprise app store.
Keep in mind, Worklight doesn't build your .ipa, .apk, or etc. It builds you compile ready resources. It will build you the folder structure and the project layers needed to build in the corresponding Native Environment (for apple, you would export to xcode, build it, and run).