I need to target older device with a cordova application and hope that https://crosswalk-project.org/ will help to solve compatibility issue with older webviews
I followed the instructions in https://crosswalk-project.org/#documentation/cordova/migrate_an_application/migrate-using-adt
xwalk_core_library and Cordova does not build for Android 4.0.3 (API 15)
I tried
crosswalk-cordova-5.34.104.4-x86
crosswalk-cordova-6.35.131.7-x86
crosswalk-cordova-7.35.144.0-x86
none of them are working,
It does build fine with Android 4.4.2 (API 19)
I saw Crosswalk Cordova does not build question and answer but answer solve latest android version and not for Android 4.0.3
Crosswalk no longer supports Android 4.0.3.
(Despite online documentation,) when you install the plugin (in cordova) you will be advised ICS no longer supported - earliest Android supported is 4.1 (Jellybean) at the time of this post.
Crosswalk Apps supports Android 4.0 and the above. Crosswalk Cordova App built by higher Android SDK should just work on Android 4.0.3 as well, The App itself doesn't have to be built by Android 4.0.3.
if you have future questions, you are welcome to visit the follow link for more timely feedback..
https://crosswalk-project.org/#documentation/community
Related
i have downloaded a react native project which uses 40.0.0 version of expo go, however my IOS simulator supports the newer version of expo go versions like 41.0.0,42.0.0,43.0.0. how can i deal with this? is it by updating the version of the project ??
that's happening because every few versions that Expo is updated, they deprecate the oldest one.
To fix this is very easy.
1 - Kill the server
2 - run expo upgrade sdk version
3 - run expo start again.
I hope it was helpful. :)
cheers
Exactly. Your problem is that your project expo SDK version is too old (which is not recommended for several reasons, one of which is that you won't be able to upload your project to the stores later).
It is recommended to always have the Expo SDK of your project updated.
I have tried several options to install IS on App Server and using different repositories but it always complains about some packages. What is the easy way to get the correct dependencies and repositories?
This is an example of the errors:
Cannot complete the install because of a conflicting dependency.
Software being installed:
STS Feature 4.2.1 (org.wso2.carbon.sts.feature.group 4.2.1)
Software currently installed: WSO2 Carbon - Carbon Feature 4.4.1 (org.wso2.carbon.core.feature.group 4.4.1)
Only one of the following can be installed at once: WSO2 Carbon -
Carbon Feature 4.4.1 (org.wso2.carbon.core.feature.jar 4.4.1) WSO2 Carbon -
Carbon Feature 4.2.0 (org.wso2.carbon.core.feature.jar 4.2.0)
What version of IS and what version of App Server are you running? I have never tried to implement the scenario you are but I could see you getting that type of error if the version of App Server you are running is on Carbon 4.4 and the version of IS is still on Carbon 4.2. The current 5.0 release of IS runs on Carbon 4.2 but I think the 5.1 release of IS runs on Carbon 4.4 and should be available before long.
Joe
I encountered the same problem described on the following question:
Wso2-emm and SAML SSO configuration
But When I Build the WSo2 EMM Project(https://github.com/wso2/product-emm) with the same maven version on Linux OS and I excute the server on the two OS Windows and Linux, the problem does not arise.
Is it necessary to Build WSO2 EMM project on Linux OS or are there specific configurations to add on windows OS?
It will support in Windows platform as well. I have personally tested this in Windows 7 and worked without any issue.
Is there any documentation available that describes the WSO2 svn structure?
It seems that the folder https://svn.wso2.org/repos/wso2/branches/ is deprecated.
Question 1: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
In the https://svn.wso2.org/repos/wso2/carbon/ folder, I'm managing to piece bits together, for example the difference between Carbon orbit, kernel and platform (see previous stackoverflow question).
In the https://svn.wso2.org/repos/wso2/carbon/platform/branches/ folder, there are 3 sub-folders:
4.0.0
4.0.2AF
4.1.0
Question 2: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
Question 3: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
Question: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
WSO2 is currently doing active development in following svn directory.
https://svn.wso2.org/repos/wso2/carbon/
Question: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
The branches in https://svn.wso2.org/repos/wso2/carbon/platform/branches/ are for the Carbon platform. The branch 4.0.2AF is for WSO2 App Factory (http://wso2.com/cloud/app-factory/)
Question: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
You can build Carbon 4.0.3 from following:
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/patch-releases/4.0.3/
You will be able to build products using the branch. That's why branch SVN URL is given in the links.
Each branch has a patch release for minor platform releases. For example: https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/
As mentioned in your answer, you can build from a tagged version also.
You can more details about product version and carbon version from the release matrix: http://wso2.com/products/carbon/release-matrix/
You can also subscribe to WSO2 mailing lists and get more information, if you have not subscribed already.
The answer to question 3 is build a checkout a tagged version (of course!!). Thanks to the answer here for pointing me in the right direction.
I was blindly following the wiki documentation which tells you to checkout a branch.
The release matrix for the wso2 platform is here: http://wso2.com/products/carbon/release-matrix/
If I want to build Identity Server 4.0.0 it seems that I need carbon 4.0.3.
Question 1. Will Identity Server only build on carbon 4.0.3, or will it build on 4.0.3+?
I have checked out the source from:
https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0
However, when I look in the orbit patch-releases folder, I only see:
4.0.1
4.0.2
4.0.5
4.0.6
Question 2. Which version of orbit patch release will I need to build for IS 4.0.0?
Question 01
To build IS 4.0.0 you need to build patch-release 4.0.3
But there can be some components from 4.0.0 up-to 4.0.3 but not 4.0.3+ So its better to build all main branch plus patch-release versions below your required version. As Ratha mentioned if you build online these jars will be downloaded if available.
Question 02
You need to build orbit patch-release 4.0.2 since it was used on IS 4.0.0
The reason for not having patch-release 4.0.3 version is there is no difference from 4.0.2 version. So same version is used during production.
Hope this will help you.
if you don't find particular version, that means product is released with older version of jars..
In your case, you might need to build 4.0.2..
Anyway if you do online build, if jars are available in the repo, they will be downloaded..You don't need to build older versions..
If not, you have to..