The Android installer do crash trying to install the exported apk.

Fri Jan 02, 2015 9:40 am

we are awaiting for the binary version since the camera and bar code functions are not working in html5 version. Is that normal?

Fri Jan 02, 2015 9:58 am

Sorry, what do you mean on html5 version? Camera and QR reader services should work in installed app only.

Fri Jan 02, 2015 11:45 am

I was making reference to html app hosted on appery.io.
You answered to my question with "only installed app" but...
the appery.io exported html/css moved to a device memory is a "installed app"?
Should it work from there?

Fri Jan 02, 2015 12:31 pm

No, you should export .ipa/.apk file and install on device.

Wed Jan 07, 2015 9:13 am

ehmmm ....
Any news?

Wed Jan 07, 2015 9:31 am

Dear Giorgio,

Unfortunately, no updates.
We'll keep posting as soon as have news.

Thu Jan 08, 2015 11:21 pm

i'm not happy...
is there a date when the problem will be investigated to provide a solution?

Fri Jan 09, 2015 10:32 am

Hi Giorgio,
Unfortunately, the exact date is still unknown.
We'll let you know as soon as have news.

Sat Jan 10, 2015 8:51 pm

Archived into my shared app "MecaDocTrack" you will find the version "v1 build 4 distribuita" (distributed).
That version is the version i had compiled with XCode and distributed to the client (waiting for the Android version that he required).
The app were perfectly working on iOS (please, don't ask me the last date when we used the app: i don't know).
V1 build 4 is the version where the APK exported from appery, was crashing the Android installer.

I tried the iOS compiled version into my iPad and ... it is not working anymore.

Also the browser test now is failing (the error message is reported here).

What's happened?
Why a compiled and distributed app is stop working?
I tested the services one at a time and they respond correctly.

Which kind of analysis are you doing if it is not working?
I was waiting from appery support answer regarding the installation and no one spoke about problems on running the app.

I'm really confused.
WHY i must spend time to debug again the app? The app was working, compiled, distributed!
The problem is a non sense.
WHY no one from Appery told me about running problems? There is someone looking for the installation problem? I am waiting for not existent support?

I'm not joking here, i pay the amount you required, i spent my time and my name with my customer assuring that Appery have a great support and that Appery is looking for the platform problem.
And now ... the distributed iOS version is not anymore working without a reasonable reason.

Is there any possible explanation?
What i have to do now?

Mon Jan 12, 2015 9:49 pm

I think it is an Appery proxy problem!!!!!!!!!!!!

As you can see from the following debug, the "bad request" error is coming from the login phase.
If you try the direct login with the browser, same url, same user, same password ... it works and you get back the expected ticket

The password is obscured here for obvious reason.
In the shared app the name and the password are written in the fields.

I'm still expecting your bugs corrections...