1. Richard Shakour
  2. PowerServer Mobile (Obsolete)
  3. Friday, 20 March 2020 12:18 PM UTC

I am trying to publish my PB Mobile App on Android for the first time.

The package has been created and opened in Android Studio (Ver. 3.6.1).

I have made the changes to the SDK settings as per the instruction in PB Powerserver Help files.

The APK has been created and posted to Google Play but still awaiting approval (CoronaV is delaying things).

When I try to run the Build from Android Studio on any device (so far tested Pixel 2 API R & Nexus 5X API) the application starts to launch but all I see is a big large white window with the Appeon logo on the top left.

Then it shuts down immediately before anything else.

Here is the error log:

2020-03-20 08:07:44.071 11477-11477/com.dct.microstaffer E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.dct.microstaffer, PID: 11477
    java.lang.UnsatisfiedLinkError: dlopen failed: library "libEonAmp.so" not found
        at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
        at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
        at java.lang.System.loadLibrary(System.java:1661)
        at com.appeon.mobile.amp.AppeonActivity.<clinit>(AppeonActivity.java:1214)
        at java.lang.Class.newInstance(Native Method)
        at android.app.AppComponentFactory.instantiateActivity(AppComponentFactory.java:95)
        at android.app.Instrumentation.newActivity(Instrumentation.java:1253)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3245)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3477)
        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
        at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2043)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:216)
        at android.app.ActivityThread.main(ActivityThread.java:7464)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:549)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:955)

 

NOTE: I already published this app on IOS in Apple Store/Test Flight and it works perfectly 100% on all IOS so far.

I tried to Google libEonAmp.so but found nothing.

Below is the brief image of the app in the simulator just before it crashes.

Again, all works in IOS just not in Android.

Any help is appreciated.

 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 20 March 2020 14:31 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 1

Hi Richard;

   Can you tell us ...

  1. Version and build of PowerBuilder that you are using?
  2. Version and build of PowerServer that you are using?
  3. Version and build of PowerServer Toolkit installed in the PB IDE that you are using?

Regards ... Chris

 

 

Comment
There are no comments made yet.
Richard Shakour Accepted Answer Pending Moderation
  1. Friday, 20 March 2020 14:51 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 2
  1. Version and build of PowerBuilder that you are using?
  2. Version and build of PowerServer that you are using?
    Product Information
    Product Version: Appeon PowerServer 2019 Build 1988.00
    Server Type: 64-bit
    Operating System: Windows
    Application Server: .Net
    Product Edition: WORKGROUP (View license details)
  3. Version and build of PowerServer Toolkit installed in the PB IDE that you are using?

Regards ... Chris

Comment
  1. Chris Pollach @Appeon
  2. Friday, 20 March 2020 15:43 PM UTC
Hi Richard;

You seem to be very current, so this problem seems strange. I would suggest creating a Support Ticket for this problem.

Regards ... Chris
  1. Helpful
  1. Richard Shakour
  2. Friday, 20 March 2020 16:06 PM UTC
Thank you Chris, I just did.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 20 March 2020 16:18 PM UTC
Awesome! I just replied on your ticket and we will have the PS tech guys looking at this shortly.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 April 2020 21:07 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 3

Hi Richard;

   Are you using an Android "simulator" or real device(s)?

Regards ... Chris

Comment
  1. mark harding
  2. Tuesday, 5 January 2021 04:14 AM UTC
Hi, I just the new update on my note 30 ultra, and now the app won't load. It starts up but then immediately crashes. Any ideas?
  1. Helpful
There are no comments made yet.
Richard Shakour Accepted Answer Pending Moderation
  1. Thursday, 23 April 2020 11:36 AM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 4

Actual physical device I got to work.  Non of the Android Studio simulator devices work.

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 23 April 2020 19:38 PM UTC
Hi Richard;

Thanks for the feedback. Yes, I have seen other developers with the same situation. The simulator does not work with your PS Mobile App but, it does on actual devices. However, it not untypical that "simple" Apps do work on the simulators.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 5 January 2021 04:54 AM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 5

Hi Richard,

Did you package a 64-bit APK and then run it on 64-bit Android OS? Please check if the file libEonAmp.so exists in paths below:
%package%\libs\arm64-v8a
%package%\libs\x86_64

The application might not work well on Simulator which generally is an x86 architecture. So we recomand you to test it on a real Android device which generally is an ARM architecture.

It seems you had reported same issue on ticket #4291, please refer to it for details.

Regards,
ZhaoKai

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.