I have a WL 6.2.0.1 application where I am developing for multiple platforms.
I increase the App version every time I release. However, How can I increase it for MobileWebApp as it always comes under version 1.0.
Application-descriptor.xml:
<android securityTest="companyTest" version="1.0.5">
.
.
</android>
<mobileWebApp cacheManifest="no-use"/>
You cannot change the Mobile Web environment's version as it does not have a version.
please ignore the version attribute seen in application-descriptor.xml.
Related
So I have uploaded a code push earlier with the target version as ">=1.0.1" (Already out on the app store)
But now I have an updated version uploaded to Testflight version 1.0.2
so I went back into the App center code push console, and updated the previously released code push's target version to ">=1.0.1 <1.0.2"
But the old update is still being downloaded when I install version 1.0.2 from Testflight. So what I want to know is, does what I did make sense? Or is there a better process for uploading new version of the app
The following table is pulled from this answer on SO:
How to deploy CodePush bundle for multiple versions?
Range Expression Who gets the update
---------------- ----------------------
1.2.3 Only devices running the specific binary app store version 1.2.3 of your app
* Any device configured to consume updates from your CodePush app
1.2.x Devices running major version 1, minor version 2 and any patch version of your app
1.2.3 - 1.2.7 Devices running any binary version between 1.2.3 (inclusive) and 1.2.7 (inclusive)
>=1.2.3 <1.2.7 Devices running any binary version between 1.2.3 (inclusive) and 1.2.7 (exclusive)
1.2 Equivalent to >=1.2.0 <1.3.0
~1.2.3 Equivalent to >=1.2.3 <1.3.0
^1.2.3 Equivalent to >=1.2.3 <2.0.0
So with ">=1.0.1 <1.0.2" it seems that you're asking for the update to affect all app versions 1.0.1 or below as well as all app versions up to but not including 1.0.2.
Currently in eclipse Mobile First 7.1 is installed. We are trying to downgrade it to worklight 6.1. We are using archive feature in eclipse (using zip) to downgrade it to 6.1. We are not getting any error while installation but eclipse is still showing MobileFirst 7.1
I am not sure on exactly you're doing there that you think you've downgraded, but note that downgrading is not possible. You cannot downgrading after upgrading your project, as the upgrade changes the application code.
I hope you made a copy of your project before upgrading.
We are using Worklight enterprise 6.2 with fix packs and we are planning to upgrade to 6.3 in the next month (beginning of May 2015). However, we see now that IBM is about to release MFP 7.
Can you please clarify to me those queries:
What is the impact on the project which has been developed on version 6.2 to be moved to 6.3 or 7?
What is the recommendation for us in terms of upgrading, should we go immediately to WL7 or to 6.3 first?
We are very close to the production and our concern that the WL7 "might" be unstable or contains issues that we might face in a critical time."Feedback would be appreciated"
MobileFirst Platform Foundation 7.0 is not about to be released - it is already released.
Lots of changes in both 6.3 and 7.0. Read the documentation to see what's changed...
6.3: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html
7.0: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html
In terms of your project structure, starting 6.3 the adapter thread pool has been removed and you are now in complete control of it. Your adapter XML will be upgraded to the new structure.
In terms of technology, starting 7.0 there is REST support together with a new authentication mechanism - OAuth. Classic authentication is as before and is still there. There are also now Java adapters in addition to JavaScript adapters, and lots more.
7.0 is indeed new, but provides you with a lot of new possibilities.
6.3 is very stable (that is not to say that 7.0 is not stable, but it's also very new).
We cannot decide for you if to upgrade or not, it sounds like you are already considering the right things to consider.
Read about the two releases.
First I installed 9.0.1 FP2 IF1 on the server (901FP2HF384_W64) and I was told that this would make dojo 1.9.4 the default dojo, but it was not. I needed to add xsp.client.script.dojo.version=1.9.4 to my XSP Property file to get it to work
Next I need dojo 1.9.4 on the client as well, both as xpinc and when doing preview in web browser so I installed first FP2 IF1 (901FP2SHF63_W32_standard) and later on also FP2 IF3 (901FP2SHF63_W32_standard) but none of these fixes seem to have added dojo 1.9.4
I did try to add xsp.client.script.dojo.version=1.9.4 to my application but I get the following error in both xpinc and preview in web-browser
No Dojo library found matching the configured Dojo library version xsp.client.script.dojo.version=1.9.4.
I ran the following code in a repeat...
com.ibm.xsp.context.DojoLibraryFactory.getDefaultLibrary().getVersion()
...and found out the following
Dojo installed using Preview in webbrowser
1.8.3
1.5.2
1.8.3
1.5.2
Dojo Installed using xpinc
1.9.2
1.5.2
1.9.2
1.5.2
What am I doing wrong here, Why is the fixes not installing 1.9.4? and how can I get 1.9.4 (same as on server) without installing separate dojo packages
Related
http://www-01.ibm.com/support/docview.wss?uid=swg21686751
On the first issue, you should definitely not need the xsp property to apply dojo 1.9.4, it should be the default. We have not come across any issue with this, thus I'm not sure what the problem is that you are experiencing. Perhaps try uninstalling & reinstalling the IF and/or FP2 and/or both?
On the Notes client issues: The 9.0.1 FP2 Interim Fix 1 fixed an iOS8 issue on the server (for XPages mobile controls) by upgrading dojo to 1.9.4 - http://www-01.ibm.com/support/docview.wss?uid=swg21657963#Domino
At present there is no Interim Fix that upgrades the dojo version on the Client - http://www-01.ibm.com/support/docview.wss?uid=swg21657963#Notes. There is no use case involving the use of XPages Mobile controls in the client, so the dojo version in the client was left untouched. It was actually unprecedented to upgrade dojo in an Interim Fix, but the severity of the iOS8 issue meant it needed to be done on the server.
You could manually copy the "com.ibm.xsp.dojo" folder from the server over to your Notes install to have 1.9.4 on both server and client
I've installed worklight 6 into an existing juno 64 bit eclipse running in windows 7. Runs great. I then install the jazz RTC 4.0.2 plug in into that eclipse environment. After the plugin is installed, there is a noticeable loss of function. The following are examples:
On the create new Hybrid app page, the option for changing the dojo library used is gone. The dialog resembles the WL5 version.
after a dojo hybrid is created, the www folder is missing from the WL project
Some dojo widgets do not work (i.e., not presented on the mobile device emulator or in resulting adroid application) like dojo.mobile.Heading
The only way to resolve is to uninstall the RTC plugin. Any suggestion on how to make this work? Using WL5.0.6.1 and same Jazz RTC plugin has no problems. We want to move to newer WL and upgrading RTC is not an easy option.
Are you using Eclipse Java EE 4.2.2? That's the only supported version for Worklight Studio (i.e. make sure you are not using 4.2.1 or 4.2 alone).
Other things I would try:
1) Use RTC 4.0.3 plug-in instead 4.0.2, that could make some difference and usually these clients have backwards compatibility with the server.
2) Install RTC before Worklight Studio, and see if it makes any difference.