We've had to remove i*/native/Frameworks/sqlcipher.framework from our SCM repository due to size limitations.
Thankfully, we have found that the mfp build command re-creates it in local copies, so this works really well.
However, the documentation here doesn't list sqlcipher.framework as ignorable - it states that the entire Frameworks directory should be checked in.
Can the documentation be updated to state sqlcipher.framework should not be checked in?
We've updated our template .gitignore project to allow for this on MFP 7.0, but it would be good to get official confirmation that this is "OK".
I've created a documentation defect to have this corrected in the user documentation topic "Integrating with source control systems" in the Knowledge Center for IBM MobileFirst Platform Foundation 6.3, 7.0 and future releases. Thanks.
Related
I have recently updated my eclipse mobilefirst studio to 6.3.0.00-20150106-1717
There after when I make any changes in HTML/Css/Js the changes are not reflected in the worklight we based simulator. Inorder to get the changes on the weh based simulator, i have to use run as -> run on mobilefirst development server.
In the previous version before this update what all changes in HTML/CSS/js was immediately reflected in the web based worklight simulator
Please advice
Update: the fix is now available from either IBM Fix Central or by updating from Eclipse Marketplace.
Duplicate of: MobileFirst Platform 6.3 - web resource changes do not get applied
This is a known regression. A fix will be available, soon.
Check back for updates in either IBM Fix Central, or via Eclipse > Help > Check for updates in the near future.
There is no local workaround.
I followed the recommended solution:
IBM Worklight v6.0 - Error while adding an application to the Mobile Test Workbench
still got the error even though my jdk seems to be already correct
I didn't see any errors in the test workbench mobile client log (emulator), which log should I be looking at?
I suppose that you are using Android 4.4 and not Android 4.4W or 4.4L which are not yet supported. And you should have made recently an update of the Android SDK tools to version 23 (you can verify by opening the SDK Manager)
Google has modified in this release the way the tools are organized and this made MTWW regressed when instrumenting.
There is a workaround: copy <android-sdk-dir>/build-tools/20.0.0/zipalign[.exe] to <android-sdk-dir>/tools.
Dominique
I had same problem. You may need hotfix or uptdate to RTW8.6.
https://www-304.ibm.com/support/docview.wss?uid=swg21678859
I need to remove the Tealeaf library from my Worklight application in order to have a lighter App (I'm using Eclipse Juno Service Release 2 Build id: 20130225-0426 with WorklightStudioPlugin version 6.1.0.01-20140311-2356 ).
I have modified my project following these steps:
In the application-descriptor.xml's Design view I've removed Optional Features > Analytics
Then I've removed the existing Tealeaf folder under native in iPhone’s environment
Finally I've removed from native\libs the library uicandroid.jar for Android
Is there any other option/configuration to set?
I receive the error below:
TLF_configurator.enable was called, but the required Tealeaf libraries are not present in the classpath.
I haven’t found any details in the official guide. There's only the procedure for adding Tealeaf, not for removing it.
If you remove the Analytics optional feature and rebuild your application/environments, it should have removed everything for you. Just changing the app descriptor XML file is not enough to do so. Did you rebuild your environment after removing the Analytics optional feature?
Also, make sure you are not enabling analytics in your code (by calling WL.Analytics.enable or setting analytics : {enabled : true} in your initOptions.js) and that you are not using the WL.Analytics API in your code.
We have a worklight i/OS hybrid application built and deployed to the worklight console using RTC jazz team build and the ant-builder ant tasks (6.1.0.1). The ipa packaging is done on a separate machine, though using the same level of Worklight Studio (6.1.0.1).
I've compared the wlapp files that are generated, and they are basically identical except for some whitespace characters (tabs, line feeds), probably due to the different environments (Windows vs AIX), and the following:
index.html
"WORKLIGHT_NATIVE_VERSION": "3921556017",
"WORKLIGHT_PLATFORM_VERSION": "6.1.0.01.20140311-2356",
"WORKLIGHT_NATIVE_VERSION": "1475155033",
"WORKLIGHT_PLATFORM_VERSION": "6.1.0.01.20140311-2356",
deployment.data
native=3921556017
native=1475155033
However, the direct update never happens when the wlapp is updated on the server.
on the WL.Client.connect call, the following json comes back as part of the response
gadgetProps":{"directUpdate":{},"ENVIRONMENT":"iphone"}
What are we missing here? What can be preventing the direct update from triggering?
Any help would be greatly appreciated.
The 6.1.0.1 iFix version 6.1.0.01.20140518-1532 from IBM Fix Central seems to have resolved this problem for us.
And what if you are not using ant, but rather built the project in Worklight Studio straight to Xcode from then install the .ipa and test Direct Update. Does it work?
From your question it is not clear whether or not you've confirmed one or the other.
Regardless, since the v6.1.0.1 build you are using, several Direct Update-related fixes were introduce; one with close proximity to the error you mention (directUpdate:{ }), so I suggest to to open a PMR in order to receive the latest available iFix (not yet available at IBM Fix Central).
I have just upgrade my Eclipse client running Juno to Worklight 5.0.6 developer edition (5.0.6.20130311-0918)
The projects upgrade fine, but when building them and deploying to the local worklight server I get a constant 'persistency data access problem' This occurs across all of my projects and has only been seen since the update.
Any idea on what is causing this problem and how to solve?
I would add a screen shot of the issue but I am not allowed
Based on your comment - in 5.0.6, the database schema has changed, so you have missing tables now. In the Developer Edition of Worklight, upgrade is not supported (this is handled when purchasing a license and using the IBM Installation Mananger for installing Worklight).
Do you mean "HSQL"? What is "Web SQL?"
In any case you will need to clean your database so that it will be re-created, this time with the missing tables.
If you use the default database provided by Worklight (HSQL), go to your Eclipse Workspace and delete the WorklightServerHome folder. Then, re-build your application.