I have been working with Worklight 6.0.0.1 and I have noticed an issue with a white bar along the bottom of the screen in all Worklight apps running on iOS 7. I know this has been mentioned before with users of Worklight and iOS 7 (IBM Worklight 5.0.6.1 - Bottom white space in iOS 7) but the suggestion (upgrading to 6.0.0.1) by Idan Adar in that thread does not resolve the problem.
Is this a known issue or is there some additional configuration that needs to be done when working with iOS 7?
Just to be specific, under "About Eclipse" the version of IBM Worklight Studio is: 6.0.0.201309091542
Thank you,
Chris
Edited to add: I am using IBM Worklight Enterprise Edition. The links to update/install are here: http://www-01.ibm.com/support/docview.wss?uid=swg27039574.
Make sure you are running the very latest fixpacks ( http://www-01.ibm.com/support/docview.wss?uid=swg27039574 ). Note that you may need more than one fixes to install.
Also, make sure you backup and delete your "native" folder so that it can build it again.
Make sure to follow the tips indicated in the tech note (same link as above).
Related
I am using a mac running on High-Sierra, I have installed MacOS server and xcode. On the sidebar of macOS services. Xcode is suppose to be shown like this:
But on my macOS server, it does not show it.
Can anyone help me with this?
The problem is related with the last upgrade "Xcode 9".
At WWDC 2017, Apple announce something that made almost every iOS developer smile, session on ‘What’s New in Signing for Xcode and Xcode Server’. It’s hard to explain, how easy it become to perform Continuous Integration for Apple platforms especially iOS and macOS using Xcode 9 and Xcode Server.
More details about WWDC 2017: Click Here
Xcode Server no longer need macOS Server app, it’s now built inside Xcode.
For continuous integreation, plase following this link.
Good coding!
I have migrated my 6.1 project to 6.3 its getting stuck on splash screen. After sometime it showing white screen.
its not calling initOptions function also or else deviceready also. Is there any solution?
Without the requested sample application to debug we cannot help further.
The only alternative is to replicate your app in a new project and application in MobileFirst Studio 6.3 by copying over the contents of the HTML, JS and CSS (and any custom native code you may have implemented).
We are facing an issue with IBM app centre app where it is not working on Android 5.0.1.
The issue is once we login to the IBM app through android device (Samsung S5 with OS 5.0.1) All our applications are not clickable and they just got highlighted and we can't go to the install page for our specific app.
It works on pervious versions of Android OS.
Worklight Server version: 6.2.0.01.20141013-1735.
I'm not sure if this is the same issue that we faced earlier with iOS8 and we have to get an ifix for it.
Reference : IBM App center not working for iOS8
Thanks.
Because you are using a very old iFix of Worklight 6.2, my first and foremost suggestion for you is to download the latest available 6.2 iFix from IBM Fix Central, and use the AppCenter client sources from that iFix.
See if the problem repeats itself as well. If yes, you will need to open a PMR (support ticket).
I am using IBM Worklight 6.0 with December 14th fix.
I am trying to use IBM App Center client for iOS8.
I have seen multiple discussions about this issue:
IBM Worklight Application Center iOS unresponsive to touch events
IBM App center not working for iOS8
I copied the project from my server, where the fix is installed, and built for iOS, but when I inspect the mobile App, I can see that the application is using Dojo 1.9.0.
> dojo.version.toString();
"1.9.0 (29469)"
I can see that the IBM App Center mobile client does not use Dojo Toolkit, but includes a dojo.js file (with a size of 1.2MB).
My question is : What are steps to build IBM App Center for Worklight 6.0, knowing that the fix is installed (Both Worklight studio and server)?
Do I need to manually change dojo.js file with a newer version? if yes, where can I find such file?
The AppCenter installation contains an Application Center Installer application project.
This is a Worklight project with the iPhone environment. The app that is generated from it is the Installer application that you need to install on a device, and from which the user will then install any subsequent applications distributed via Application Center.
Make sure you are using the provided Worklight project; there are no additional changes to be done to to project (other than using your own bundleId, ...).
It could be that you are missing the Dojo library in your workspace?
You can generate it by creating a new Worklight project and application using the Dojo wizard in Studio.
When you received the fix, it contains a new project for IBM app centre.
You need to get this project and import it to your Eclipse Environment and rebuild the IBM app centre (APK and IPA) files.
You have to redeploy these files to IBM app centre console and re-download them on your iOS8 devices.
I believe the iOS8 fix starts from version V6.2, and we have downloaded fix v6.2.0.1.
So, I'm not sure about V6.0.
Please verify with IBM.
The content assistant is not working.
I'm working on OSX, Titanium Studio, iOS & Android mobile app and have tried the following:
Installing the following SDKs: 3.2.0, 3.2.1, 3.3.0.
Tried reverting between those versions.
Checked the Project Natures (mobile - primary, mobile module, are checked).
Tried every option on the Project Build Path.
Of course tried to build the project again and again.
Check the content assistant preference both in the main preference and in the project properties.
Are the any more suggestions?
I believe this is a bug in the 3.2.0GA SDK (3.2.1 and 3.3.0 are not official releases yet). As far as I have heard it is known and should be fixed in the next SDK update. Only question is when this update will be out.
You can get content assist back by reverting to 3.1.3GA, but that doesn't help you much if you need features from 3.2.0GA.
EDIT:
The issue is described in this JIRA-ticket and as it mentions should be resolved in the upcoming 3.2.1 release.