I recently migrated to Worklight Studio 6, and the application-descriptor.xml of my app is being flagged due to the width, height, and worklightServerRootURL elements. I've looked in the documentation but haven't found a mention yet of how to migrate these elements for Worklight 6. Are there replacements?
The mentioned elements have been removed (worklightServerRootURL) and moved (height, width - into the Adobe Air element, if the environment exist in the project).
Your application-descriptor.xml should not flag you about these. If you do get flagged (do you mean you get an error or warning?), it means something in the upgrade process of your project has gone bad.
In any case, to overcome this simply remove the offending elements.
That said, because this could indicate on a bad upgrade other things may have gone wrong as well. If you can add any more information it will help.
Can you share your project? (export it as .zip file from Eclipse)
Related
I am trying to use UWP(Community Toolkit) TabView Control, but it's throwing below exception:
Cannot find a Resource with the Name/Key UseSystemFocusVisuals [Line:
35 Position: 91]'
Min Version and Target Version both are set to Build 16299. As per this MSDN documentation, it supports device family Universal, 10.0.16299.0 or higher
Windows 10 OS build is 17763. If I change the target version to 17763 then it's working as expected.
Any reason why it's not working when the target version is set to 16299?
Strictly speaking this isn't the UWP control but rather Windows Community Toolkit control. As it isn't made by Windows team the documentation is based on the human input and clearly there can be errors in it. It may also be a bug, the best thing to do is to submit the issue to their github: https://github.com/windows-toolkit/WindowsCommunityToolkit/issues
With the input from #Ivan, I checked for similar issue on WindowsCommunityToolkit GitHub site and seems that this issue was already reported.
According to the discussion on the issue, Fix is already implemented but will only be available when a new version of the toolkit is published. So until then if anybody else wants to have a fix, you need to define UseSystemFocusVisuals in your App.xaml as below:
<x:Boolean x:Key="UseSystemFocusVisuals">True</x:Boolean>
I have a base app that I modify slightly for each customer. I have been using version control to switch between customers' versions in the same working directory and restart Eclipse. However, I now want to have multiple versions of the app next to each other (in separate directories). They all have the same app ids and adapter names, but different contexts.
The problem is, as soon as I deploy a second app, the first one gets overwritten by it. Say:
I deploy version 1, open it (common resources) -> it shows version 1.
I deploy version 2, open it -> it shows version 2.
I open version 1 again it -> it now shows version 2.
I presume it has something to do with the app names/id's being equal. I tried switching the Worklight Console DB from Derby to MySQL, but to no avail.
I'm not sure I've tried all possible combinations, but right now version 1 shows version 2 when I click on common resources and version 1 when I click on an actual environment.
This clearly seems to be a bug or a very obscure undocumented peculiarity, doesn't it? Any help with this?
Worklight Studio version is 6.2.0.00-20140918-1910.
I was finally able to reproduce the error in the question. It does appear to be an obscure bug indeed...
I see no workaround other than a restart of the server (a reboot of Eclipse is not required), via the Servers view > green "play" button.
My suggestion is to open a support ticket (PMR) to have this further investigated and possibly have a fix delivered.
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'm using IBM worklight 6.1 and eclipse Juno for my mobile app project. This is a first time I got this kind of symbol on my eclipse. Can I know what symbol is this?
Thanks a lot in advance.
The markings overlayed on the folder and file icons are called decorators. The ones depicted in your screen shot are not coming from Worklight.
The decorator overlayed on the folder icon is called staged or partially-staged.
http://wiki.eclipse.org/EGit/User_Guide/State#Label_Decorations
staged - The resource has changes which are added to the index. Not
that adding to the index is possible at the moment only on the commit
dialog on the context menu of a resource.
partially-staged - The resource has changes which are added to the index and additionally changes in the working tree that are neither in the index nor in the
repository.
The decorator overlayed on the files icon is called added.
http://www.rorycullen.com/blog/2009/07/guide-to-subclipse-decorator-icons/
The “plus” sign indicates that this is a new file that did not exist
before.
You may have enabled some source control plug-in in your Eclipse installation.
In any case, not related to Worklight.
While changing the dojo version from 1.3 to 1.7.3, I simply replaced all my dojo 1.3 folder files with dojo 1.7.3. After rebuilding my web application, I am getting error hxrFailed at dojo.js, line no 15.
What is the wrong that I am facing here? Do I need to change any existing code. Is there any document to refer for all the required changes.
Please help me to get out from this issue.
Thanks,
Sridhar.ch
Lots changed and there are some lengthy tutorials to help you migrate. Check out the documentation tab on Dojo's website:
1.x to 2.0 migration guide:
http://dojotoolkit.org/reference-guide/1.8/releasenotes/migration-2.0.html
Updated buildsystem tutorial:
http://dojotoolkit.org/documentation/tutorials/1.8/build
In theory the current (1.8) build system is backward compatible until 2.0, but in practice I'm not sure it is 100% backward compatible because my 1.6 build profile didn't work with 1.7.x and up. I didn't try that hard to get it to work though.
I have gone through the same. the xhrFailed error occurred for me for multiple reasons. One of the reason was a missing a file in the define as below:
define(["something/was/missing/here"],function(){});.
Another cause for the same error occurred was when a folder in a path of a dependency was renamed but not updated in the application build profile. (This case only if your are doing custom builds).
See if that is the case!