IBM Worklight SimpleDialog platforms limits - ibm-mobilefirst

I am using Worklight 6.0 for an application working on 4 platforms (iOS, Android, Blackberry and Windows Phone 8).
While using WL.SimpleDialog I can notice today that the handler button option/callback does not work on Blackberry 10. Also when reading the documentation at http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.0.0/com.ibm.worklight.help.doc/apiref/r_wl_simpledialog_show.html there is nothing that mention that.
For the test on Blackberry, I am using Webworks 10 version 2.2, and I am inspecting the device.
I call the SimpleDialog this way:
WL.SimpleDialog.show("Alert", "Popup message", [{text:"ok", handler: function() {
console.log("hello") ;
}}]);
The message "hello" is not appearing on console after I press the button and there are no errors appearing on console too.
Update : One more detail: I checked an old version, compiled 1 year ago with webworks 1.0, and handler is working for the old version.
Is this an issue related to Worklight 6.0 and Blackberry Webworks 2.2 ?
Do you confirm that the handler option is not supported for Blackberry ? also is it supported for Windows Phone ?

Update: Fix for WL.SimpleDialog is available starting November 25th, 2014. You should be able to download the latest 6.0.0.x iFix from IBM Fix Central (or request it via a support request (PMR)).
Per the Common UI Controls training module (slide #13):
When you use WL.SimpleDialog in Windows Phone 8, you can use at most
four buttons in each instance of WL.SimpleDialog.
When you use WL.SimpleDialog in Android, you can use at most three
buttons in each instance of WL.SimpleDialog.
As for the callback in BlackBerry 10, it should work. Are you getting any errors?
Also provide your SimpleDialog implementation, i.e. what are you calling and how you are calling it.
Edit: Make sure you have added all required plug-ins: org.apache.cordova.dialogs AND org.apache.cordova.invoke.
Edit #2: the callback not getting invoked has been confirmed as a defect. To receive a fix, please open a PMR.

Related

Developer unlocked windows phone gets locked for no reason

I have 2 windows phone devices on my account that I use for testing. But they get locked for no reason.. I have to unlock it almost everyday. It even happened twice in one day. I haven't figured out what is causing this...
Is anyone experiencing this same issue?
**** UPDATE MESSAGE ****
This is the latest bizzare update on this bug... I've pasted my post in Microsoft Forum below:
I'm experiencing a very strange bug that I don't know if it is on the Windows Phone SDK or in Visual Studio.
I have 2 WP 8.1 devices to test an app that I'm developing. This was the sequence of events that led to this lock down:
Suddenly one phone that I used the most started to ask, almost everyday, to develop unlock the device...
Then the other phone started to do the same.
Now everytime I make a release version and run it targeting Device in Visual Studio, VS 2013 crashes... And the phone gets developer locked again.
Then I found a workaround that was to use the Application Deployment tool from the SDK only to test the release version. (Debug version it deployed without any problems on the device)
Today I forgot the manually deploy the XAP and clicked run in VS. VS crashed... Then I tried to deploy using the SDK tool it said that phone was locked... I unlocked it and clicked on the Deploy button again. Then the error: The maximum number of developer applications on this phone has been reached appeared.
I've uninstalled the app from the Windows Phone device manually and tried again and the same error occured.
I tried the other test device and had to register it again and got the same error.
Now I can't deploy any release version and I don't know how to fix this issue.
Do you know how can I fix all this Visual Studio bugs? I can't seem to find anyone else with the same problem as I'm having.
No, i have three unlocked devices in my account but one wp8.1 and other two win10, if you can upgrade your wp8.1 devices to windows 10 do that using that app because windows has inbuilt feature to developer unlock device, so your device won't get locked again automatically.
if you don't want to upgrade to and need assistance go to this link
this link requires you to login with your outlook account or may require you to login with your windows developer account.
and extra information if don't have windows developer account and want to publish your app go to this link from your windows mobile device or directly search for "Dev Share" App in windows store.

MobileFirst is_connected, is_disconnected events do not work

I'm using MobileFirst 7 to develop a hybrid Windows8 + iPad app.
The event WL.Events.WORKLIGHT_IS_DISCONNECTED works fine if I start my app with server down, but if I start app with server up (online) then I stop server the event is not risen.
This happens in both Windows8 and iOS (ipad) environments.
A regression was introduced in MFPF 7.0 causing the WORKLIGHT_IS_CONNECTED and WORKLIGHT_IS_DISCONNECTED events to fail (APAR PI38012). It was fixed in a subsequent iFix release.
If you are using the Developer Edition then make sure you are using the latest build in Eclipse > Help > Check for updates.
If you're using the Consumer or Enterprise Editions then get the latest iFix from IBM Fix Central website.
The date of the fix should be from 2015-04-08 or later.

Worklight, Adapter-Based Authentication for Android, app does not exist on the server

Im new to Worklight, Im trying to run the AdapterBasedAuthenticationProject from the tutorial of IBM worklight. Sample here
After deployed the auth-adapter and build the app, this app run ok on the Worklight console. However, when I make the android version and run on virtual machine, I can not get the secret data.
When I click on "Get secret data" button on android, error occurs
[ERROR ] FWLSE0332E: The application AdapterBasedAuthApp for the environment android does not exist on the server. Cannot register this client. [project AdapterBasedAuthenticationProject]
Image here
Looks like you are using JRE 1.8 (Java 8). Note that Worklight does not support Java 8 - downgrade to either Java 6 or 7.
Make sure you have:
Added the Android environment
Deployed the Android environment (right-click on the your-app\android folder and select Run As > Build and Deploy)
Those are crucial steps in order for the server to recognize a request originating from Android
Also, I don't understand what do you mean by "virtual machine", as it is not obvious from the screen shot. It just looks like a resized browser window.
I encountered similar issue today. In my case Java version was not the issue the issue was incorrect wlAppVersion number in wlclient.properties,
make sure it is same as in application-descriptor.xml.

What Version of Windows Mobile 6.5 is on my Device?

I have a Symbol MC 75. It is running Windows Mobile 6.5, but there are several updates after the basic Windows Mobile 6.5:
Windows Mobile 6.5
Windows Mobile 6.5.1
Windows Mobile 6.5.3
Windows Mobile 6.5.5
How do I know which one I am running?
I went to the about page for my device and it just says Windows Mobile 6.5. Does that mean I only have the 6.5 or is it not bothering to show me the update version?
NOTE: The CE OS version is: 5.2.21840 (build 21840.5.0.60) in case that helps.
Note 2: The reason I care is that there is a Developer Tool Kit that is targeted for 6.5.3 and I want to know if I can use it.
It looks like builds 5.2.28xxx are for 6.5.3 and 5.2.21xxx are for 6.5
Sources:
source 1 (and in case the google-cached page doesn't show here's the original)
source 2 (read the comments areas too)
Looks like the start button is on the bottom with 6.5.3. Since it is still on the top corner I am guessing I am on 6.5 or 6.5.1.
Tap on Start>Settings>System>About

Safari3 and Safari4 side by side

I've just read about the release of Safari4 (beta) and its much improved Javascript engine.
I was planning to start playing with it, but I am wondering if anybody knows if both Safary 3 and Safari 4 can be run side by side.
You could run Safari 3 and use the nightly builds of Webkit to test the new engine. You'd be still missing the new features like Cover Flow and Top Sites though.
Try this
Safari normally use the Web Kit
framework found inside Mac OS X to
render web pages and execute
javascript. This means that if you
preserve an old version of Safari to
run it on a newer version of Mac OS,
it will use the newer Web Kit found in
the system and you will get the same
results as with the newer version.
However, the link has some stand alone versions that you can install.
There's also this which shows how to create your own stand alone version.
Beatnik Pad has a quick tutorial that shows how running Safari 4 Beta and Safari 3 side by side can be accomplished.