I have upgraded my IBM MobileFirst server 6.3 to 7.1. The server has iOS, Android and Blackberry applications (environments) running.
After the upgrade of OS from Windows 2008 R2 to Windows 2012 R2 Datacenter and MobileFirst 7.1, all the applications are running fine except Android.
There is nothing in the logs on the server side, however, on the LogCat I saw below errors:
02-08 13:44:02.577: E/libEGL(4044): validate_display:255 error 3008 (EGL_BAD_DISPLAY)
02-08 13:44:03.271: E/AndroidProtocolHandler(4044): Unable to open asset URL: file:///android_asset/www/default/js/settings.js
02-08 13:44:32.323: E/NONE(4044): Uncaught Exception: Uncaught ReferenceError: pageinit is not defined at (compiled_code):599
"settings.js" is not a MobileFirst-supplied file. It is also unclear from the supplied exception where in your code is the uncaught reference error.
Suggestions:
Remove the "native" folder and re-build the Android environment, or
Preview the Android environment in a browser (from the console), and check the Chrome DevTools console. See if the error happens there as well.
Right now nothing indicates a problem in MobileFirst, rather in the app.
Related
i recently converted my mfp studio project to mfp cli cordova project.
when i preview my project everything work fine except "WLResourceRequest is not defined" that log to the console.
enter image description here
i noticed that the web preview works fine, but the mobile browser simulator not working and logs the same error
Same problem. I have a ionic project. This was working till I installed MFP 8.0 beta
Post that I m unable to make any adapter calls.
It doesn`t work in Chrome, but it works on my device. Using MFP 8.0
My development platform iOS. My development SDK 5.1.0. I run into a strange error of [LiveView] Server unavailable while testing my app via development ipa on device. Before this i always made development ipa through Titanium Studio but due to some configuration problems of iOS sdk in Titanium Studio i switched to Appcelerator Studio. I am able to make development ipa successfully from Appcelerator Studio but when i install it on my device and run there is always error of LiveView server unavailable. Has anyone else faced this problem then do reply i have to send test build to my client for testing.Error Image
You have enabled LiveView for your app, which doesn't work if you manually install an IPA to your device.. you should disable LiveView!
It is the little green icon with the eye in Appcelerator Studio in the toolbar!
I am trying to upgrade to MF 7.1 from MF 7.0. After upgrade, when I deployed the application on server and preview the Android App, it displays below alert message:
I have following below steps to upgrade the project:
I used new eclipse for project upgrade: eclipse-jee-kepler-SR1-win32-x86_64.
Installed RTC 4.0.2 Client into the eclipse and restarted it.
Change the Workspace Text File Encoding to UTF-8.
Imported the MobileFirst 7.0 project from RTC.
Deleted "wlBuildResources" and "wlPreview" folders from %temp% ditecroty.
Installed MobileFirst Stidio IF : 7.1.0.0-MFPF-StudioP2-IF201509132345.
Restarted the eclipse.
Project upgraded to MF 7.1 successfully.
Installed the ADT To Eclipse using the update site and restarted the eclipse.
Right clicked on project name and Ran on MobileFirst Development Server.
Open the console and previewed the Android application and it displays the following alert: gap_init:2.
I have deleted , regenerated project but everytime I am getting this error. I have create a new project also
but I am getting the same alert message on previewing the Android application.
This happens due to a regression and is taken care of in APAR PI50036 CORDOVA "GAP_INIT:2" ERROR WHEN PREVIEWING ANDROID IN MBS
To receive the fix once it is available you should open an IBM PMR (support ticket) and mention the APAR number above.
FWLSE3210W: Environment: android of application BBQ version 1.0 has
been deployed with a different version of the native MobileFirst SDK.
Direct updates will no longer be available for existing clients with
other versions of the MobileFirst SDK. To continue to use direct
updates, increment the app version, publish it to the public app
store, deploy to the server, and (optionally) block/notify older
versions of the app to enforce customers to upgrade to the new version
from the app store.
I am seeing the above warning again and again. And it doesnt seem to be related to the version difference between my worklight studio and worklight server.
I have created a MobileFirst Project in MobileFirst 6.3.
I have a remote MobileFirst 6.3 server.
When I deploy the iphone wlapp file first through the worklight console it goes through successfully but when I deploy the android wlapp file of the same app, it shows me the above warning and similar thing happens when I upload the android wlapp file first no issue but when iphone wlapp file is uploaded it shows the warning. Could someone tell me what this warning really is?
This is a false-positive warning message that you can safely ignore.
If you'd like it gone you can also download the latest MobileFirst Platform Foundation 6.3 iFix from IBM Fix Central where it has been fixed.
I'm using Worklight Studio 6.1.0.00-20131219-1900 and trying to build an app for Blackberry 10
I create a new Worklight app (no customizations other than adding the blackberry 10 environment), run it on the Worklight server, and use ripple to build and deploy to the blackberry 10 simulator.
The app installs on the simulator, But when it launches, I immediately get a JavaScript error:
[ERROR] Error initializing Cordova: Extension Device not found
This is possibly related to a problem seen with Cordova 3.1 (see: Error initializing cordova: Extension device not found in PhoneGap 2.9.0 and blackberry10 webworks application) but I'm not seeing any solutions.
Is there any way to get Worklight 6.1 apps to work on Blackberry 10?
My guess is that your issue is mentioned in infocenter
http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/index.jsp?topic=%2Fcom.ibm.worklight.dev.doc%2Fdevref%2Ft_creating_a_new_ibm_BlackBerry_10_environment.html
basically, did you do the "ant qnx copy-extensions" command ?