on 01-19-2016 1:06 PM
Hey there
I've built a custom SAP Fiori Client using the script provided within the KapselSDK.
I had to edit a few scripts, because of plugins renaming etc, but the Build of the app worked. When I now open the app and enter my fiori launchpad url, following screen is shown:
After I try to write something in the inputs, the app crashes. The crash log of the Fiori Client:
Thanks,
Fabian
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the exact same problem, app crashes on first user input, e.g. trying to type in the URL of the Fiori Launchpad.
Works on the emulator, but crashes on the phone.
Node: 6.0.0
Cordova: 6.0.0
MobileSDK3 SP 12 pl 3
I build the source as unmodified as possible.
There are errors in logcat:
a lot of google-breakpad, leading up to:
06-15 15:41:58.730 4506 4581 W chromium: [WARNING:keycode_converter.cc(91)] empty code string
06-15 15:41:58.731 4506 4506 E chromium: [ERROR:xwalk_autofill_client.cc(172)] Not implemented reached in virtual void xwalk::XWalkAutofillClient::OnFirstUserGestureObserved()
...
06-15 15:41:58.908 4506 4581 W google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ###
06-15 15:41:58.908 4506 4581 W google-breakpad: Chrome build fingerprint:
06-15 15:41:58.908 4506 4581 W google-breakpad: 0.0.1
06-15 15:41:58.908 4506 4581 W google-breakpad: 12
06-15 15:41:58.908 4506 4581 W google-breakpad: 7d26c012-4f20-450a-b207-c04dc7980276
06-15 15:41:58.908 4506 4581 W google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ###
06-15 15:41:58.909 4506 4581 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 4581 (Chrome_InProcRe)
06-15 15:41:58.961 385 385 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-15 15:41:58.961 385 385 F DEBUG : Build fingerprint: 'lge/g4stylusn_global_com/g4stylusn:6.0/MRA58K/16054235401ba:user/release-keys'
06-15 15:41:58.961 385 385 F DEBUG : Revision: '7'
06-15 15:41:58.961 385 385 F DEBUG : ABI: 'arm'
06-15 15:41:58.961 385 385 F DEBUG : pid: 4506, tid: 4581, name: Chrome_InProcRe >>> pl.arvato.fioriclient <<<
06-15 15:41:58.961 385 385 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-15 15:41:58.998 385 385 F DEBUG : r0 00000000 r1 00000001 r2 29189fbc r3 29189fbc
06-15 15:41:58.998 385 385 F DEBUG : r4 00000001 r5 99af78e4 r6 99af78e0 r7 00000000
06-15 15:41:58.999 385 385 F DEBUG : r8 99af798c r9 00000000 sl 99af7937 fp 99af7990
06-15 15:41:58.999 385 385 F DEBUG : ip b6d825dc sp 99af78c0 lr 9c07a387 pc 9c5d3998 cpsr 60000030
06-15 15:41:59.000 385 385 F DEBUG :
06-15 15:41:59.000 385 385 F DEBUG : backtrace:
06-15 15:41:59.000 385 385 F DEBUG : #00 pc 008fb998 /data/app/pl.arvato.fioriclient-1/lib/arm/libxwalkcore.so
6-15 15:42:00.178 385 385 F DEBUG :
06-15 15:42:00.178 385 385 F DEBUG : Tombstone written to: /data/tombstones/tombstone_01
06-15 15:42:00.178 385 385 E DEBUG : AM write failed: Broken pipe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe the problem is related to a recent update to the Android System Webview.
The problem occurs when the version is 51 or higher on Android.
The problem seems to only occur with the Fiori Client built with SP 12.
Note the problem does not occur with the Fiori Client available from the Google Play store as that was built off of SP 11.
A short term workaround for this is to go into Settings > Apps > Android System Webview and choose Uninstall Updates.
This issue appears to be reported here.
https://crosswalk-project.org/jira/browse/XWALK-6997
I also believe the next PL for SP12 of the Kapsel SDK will contain a fix for this. I will post again when the patch is available.
Regards,
Dan van Leeuwen
I believe the latest PL is now available for SP 12 that should contain a fix for this problem.
SP 12 PL05 available at
Regards,
Dan van Leeuwen
Hi,
I believe at the moment only SP12 PL04 is available.
This issue is caused by a new update of the Android System Webview app published at 06.03. As Daniel posted before the version 51 causing the problem.
However do not recommend to uninstall the Android System Webview app, as many other apps are built on this. So uninstalling it can cause other apps to fail.
The issue is only a problem if the build apps are using the XWalk Cordova plugin and not the internal webview browser. We have used the XWalk Cordova plugin as it has support for Android versions under 4.4. The Android versions under 4.4 are not working correctly when Cordova is using the webview plugin, as under 4.4 the webview has not built on chromium.
This Android System Webview app version 51 is not functioning correctly with the XWalk plugin used for Cordova to build your apps. The correction is available with the new XWalk version 21. At the moment the latest XWalk Cordova plugin we have used is built with the version 18 of the core XWalk.
You have two options: Wait for the new plugin built with XWalk version 21 or build your own XWalk plugin with the new core version 21. (We did this, and our app is working again.)
So as the Cordova XWalk plugin is still not yet corrected officially, we have to wait a while till the new version of the Cordova XWalk plugin will be included in a new SP/PL of the SDK.
Br
Richard
SDK SP 12 PL 05 was only available as a production version yesterday.
As a trial download [1], only SDK 12 PL 04 is available, but that archive was broken yesterday:
ERRORS:
Unexpected end of archive
Physical Size = 1155230663
(I've already reported that problem to the SAP Store team (ticket 1000019803). Supposedly they are working on it.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Fabian,
First, Dan is much more experienced than I am and I would take my lead from him. For the crash, you need to attach the logcat. Something in it may seem innoculus to most people, but may contain something we have seen before and give us some clues. The first screen shot above looks like the container isn't rendering anything. I assume you have checked the launchpad out in Chrome and it's fine? The Fiori Client log looks like there could be a backend setup issue with cachbuster, but not sure the URL looks correct. Have you tried just building the client normally without any edits and checked if it worked first?
Regards,
Kevin
I don't know why you are seeing those crosswalk errors. I found this though after a Google search.
It might be something to quickly try the solution provided.
Hope that helps,
Dan van Leeuwen
Any idea?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there
Yesterday I've built it again, with a fresh installation of the MobileSDK. At this time I hadn't to change anything for the build, everything worked. But when I start the app, I still get the same login page bug.
On the old computer, I've changed a name of a package, because the old one was no more available and had to downgrade a plugin.
The SDK Version was SP10 and Cordvoa version 5.2.0 and the nodejs version 0.12.9. I've tried it on 2 devices once LG G4 and Sony Xperia Tablet with both Android 5.1 respectively 5.1.1.
Regards and thanks
Fabian
Hey there
I've done a little of custimization, I disabled the passcode, as written in your tutorial. The Image from the screenshot is our fiori launchpad, we did some theming there, but in the browser it looks normal.
I didn't examine the logcat, but I tried to connect it to the JavaScript console, but as soon as I inspect the WebView the app crashes. It also crashes if I try to enter username or password.
Maybe it has something todo with cachebuster? Or any notes missing?
As information, the Fiori Client is integrated in the Worx Home environment of Citrix.
Is there any other way to build a custom Fiori Client? Like with the Hana Cloud Plattform?
Regards and I appreciate
Fabian
I think viewing the details of the crash in the Android logcat might be helpful.
I suppose you could also try commenting out the fioriURL parameter in the appConfig.js file assuming you have set that variable to your Fiori Launchpad. That way you could try it out in demo mode and perhaps that would further help isolate the problem.
Another thing you could try would be to download the Fiori Client from the app store rather than building it yourself.
Regards,
Dan van Leeuwen
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.