We recently implemented MobileFirst 7.0 IF201609291531 iFix and started experiencing a windows 8 app connection issue when a new runtime is created on the server and a windows8 app uploaded:
The windows8 App is deployed on a device via App Center
When the windows8 app attempts to connect, the server log records the message:
FWLSE0332E: The application some_app for the environment windows8 does not exist on the server. Cannot register this client.
I double checked that the app was in fact deployed on the server, I confirmed the version number, app id, and server details in the wlclient.properties file. The same build process also deployed an Iphone and Android app, both of which works and connects correctly.
I decided to change the windows8 application access to "Active, notifying" just as a test. The console did not save the message, and when I looked at the log, it recorded:
000000e5 com.ibm.worklight.admin.actions.BaseTransaction E Result: newruntime: mobileFirstServer///XX.xx.X.xx: There is no deployed application with name 'some_app-windows8-2.0.25'
I managed to set the application access for both the iPhone and Android apps without any problems.
This behaviour is only evident on any new runtimes created since the ifix was installed. When I upload the windows8 app to a runtime that existed before the ifix it connects as expected.
I've tried this on multiple MobileFirst servers with the ifix loaded and the behaviour is consistent across all of them.
My build setup is as follows:
The binaries are built using MobileFirst CLI (initially with IF201607241420, and then with IF201609291531) using Jenkins
The binaries are then uploaded and deployed to the MobileFirst server using the worklight_build.xml ant script
Server OS: RHEL 7.0
MobileFirst configuration: standard Liberty profile
DBMS: MySQL
Has anyone experienced this before? Could it be a database or permission issue?
Our sys admin is planning on removing the ifix on Monday, after which I'll run another test to see if it resolves the issue. I'll post the result of the test here.
It's clear you are experiencing some kind of a regression with the latest iFix. I suggest then that you'll just open a PMR. This is not a question for Stack Overflow.
I have found a work-around for the issue.
It seems the issue occurs if a new runtime is deployed via the ant scripts, and the application is also deployed via ant scripts (no manual deployment was done). When I manually deployed the application via the web console it resolved the issue. This manual upload seems to only be required once, after that the app continued to connect as expected even with subsequent ant uploads.
Related
I have an Electron app in the Mac AppStore that is essentially just a wrapper around a hosted web app. A few months ago one specific thing has stopped working in this app. I'm using redux-offline to sync changes to the server and this is just not happening any more.
It's working when running it outside of Electron - in any modern browser.
All other requests are working fine.
It's working when debugging it locally.
It's working when running the built version locally.
BUT it fails in the published Mac App Store version. I'm not catching any errors in my logs (server-side or client-side). I just upgraded to the latest Electron (electron#4.1.4, electron-packager#13.1.1) hoping it would solve it - to no avail. I don't even know how to properly debug it since it's only failing in the published version.
Any ideas? On causes, solutions or ways to debug it?
Seems like your application closes by itself. Check all of app.quit executions. For me issue was that app.requestSingleInstanceLock() returns the wrong value for Mac Store build. Please check this issue, if the problem is related to app.requestSingleInstanceLock().
I am new to IOS development and have come across an issue and need some help.
I am trying to create an iOS application to target to work on iPhones. I am using MeteorJS, ReactJS with MongoDB for a database.
When I run the ‘meteor run ios’ command I am able to get the Xcode project.
I am also able to load the Xcode project within Xcode and generate the IPA file to demo on my iPhone using ITunes from my MacBook Pro.
When I try to run the application from my iPhone everything works - meaning I was able to connect to the local database (localhost:3001 mongodb). Also, the tests on the application only work when my phone is connected to the Mac.
Now, when I try to export the application and want a colleague to test the iPA file does not work. The IPA file gets installed on the colleague’s phone, however application does not work.
I think I’ve followed the process as required for Adhoc Provisioning profiles however I am not sure whether Im doing this right - because possibly the database is not being packaged with the IPA file?
Could someone please help / Guide?
When running a build produced by meteor run ios, the application on the phone tries to connect to a server running locally on your machine over the networked formed on the physical Lightning cable connection.
While you can configure the iOS client to connect to your machine over your local network, this solution introduces other problems you won't expect. Deploy your application to Galaxy, configure your iOS settings to use the URL on Galaxy, and make a production deployment of your iOS application. Then the iOS application will try to connect to an accessible public Internet URL (your Galaxy deployment), rather than your inaccessible local machine.
See the documentation for details.
meteor run ios-device --mobile-server=http://ip:port
worked for me
I have two applications developed on WL 6.2.0.1. And I was building my iOS projects using xCode 6.3.1 as I wasn't facing any issues on iOS (All OS versions)
When I upgraded my xCode to 7.3.1. all my iOS projects that are running on iPhone/iPad with iOS9+ starts to fail and it not even connecting to my WL server anymore.
Any invocation I make it failed and I see no logs on the server, meaning it is not even reaching it.
If I tested the same build that is done on xCode 7.3.1 but with iOS8 it works.
When I revert back my xCode update as I have a time machine, all start working again on All OS versions.
Is there a known issue with WL 6.2.0.1 with new xCode? I have been searching and couldn't find anything about this.
Server version: 6.2.0.01.20141013-1735
Starting with Xcode 7 and iOS 9, Apple now requires ATS (Application Transport Security) by enabling TLS 1.2 on the server and working with HTTPS on the client. That is why all your requests are failing - because the client & server are misconfigured.
During development, you can disable ATS. See here: https://mobilefirstplatform.ibmcloud.com/blog/2015/09/09/ats-and-bitcode-in-ios9/
For production-time, you'll want to read this: https://mobilefirstplatform.ibmcloud.com/blog/2015/09/07/preparing-ibm-mobilefirst-platform-server-app-transport-security-ios-9/
I am using IBM worklight 6.0 for building a hybrid application. My application is running perfectly on IOS 7. When I migrated the same code to Xcode 6 beta for IOS 8 build, only the splashscreen with loader came up and the app hangs. From the logs I saw that the application goes to skinLoader.html. None of the events are called.
To my curiosity I created a dummy worklight iphone environment and ran it on IOS8 and again the app got stuck on the splash itself.
I had a deviceready event on the html which was not called. So I am curious to know if there are other issues other than the userAgent issues with the worklight for IOS8.
It is a known bug in iOS 8 beta 1 in Cordova applications and it is expected to be fixed in upcoming releases.
Applications that use Apache Cordova/PhoneGap are broken due to a bug that causes the window.navigator.userAgent object to become undefined when window.navigator is replaced by a pure JavaScript wrapper object.
via
and it is already answered in this forum.
A fix for the stuck-at-splash is provided in an iFix release from September 18th via IBM Fix Central.
For more information please see this question: Worklight 6.1 and iOS 8
Scenarios:
If a user has already upgraded to iOS8 and the application got stuck on the splash screen, AFAIK the way to handle it is to either:
Uninstall/re-install the application from the App Store.
Install a newer app version (see below) from the App Store.
If a user did not yet upgrade to iOS8, it is best to use the fixed Worklight Studio to generate an updated app, increment its version and re-publish it. Then, Remote Disable the existing version and direct users to install the fixed version from the App Store; the fixed version should then continue to work after upgrading to iOS8.
Can the code developed and running in Websphere application server v5.1 run in Websphere application server v6.0/6.1/7.0 without any problems?
My scenario:
Originally, the application developed using Java 1.4 and WAS v5.1. As part of change request, we are going to do some changes in that application.
Currently, in my development environment i have RSA(Rational Software Architect) 7.5. It complaint with only WAS v6.0/6.1/7.0. So i can work with one of these WAS version.
Which version i can choose to work for development WAS v6.0/6.1/7.0?
But finally the developed/changed code in WAS6.0/6.1/7.5 will be deployed in WAS v5.1(PRODUCTION) only. I am worried about whether code will run properly or not.
Will i get any complaint problem in this scenario?
Thanks in advance.
The most important is not to change your compiler settings from 1.4 to the RSA 7.5 default which I believe is 1.5.
In case you compile your source code with higher version of Java and deploy it in a Container which runs on a lower version you are going to have trouble.
Generally it is safe to run and test your legacy app on a higher WAS version but keep your eyes on the compiler settings as I mentioned.