Home
>
WinDev Forum
>
Topic
[WDM] All Android Apps are not stable. Crash reproducable
Posted by wilr
|
[WDM] All Android Apps are not stable. Crash reproducable February 20, 2019 01:44PM |
Registered: 5 years ago Posts: 3 |
After creating a WDM22 app, we experience problems in the app while opening it after being in the background for a while.
After using the app, using other apps and reactivate the app again, we get a popup from Android with the info that the Application is stopped and we get an error like:
We tested on several Android Devices (Samsung S5 NEO, Samsung A5, Samsung A8 and Samsung S9) with several Windev Mobile apps.
The phones are provided with the (for them) latest OS.Even the apps from the examples and from the Google Store that are published by PCSoft give this kind of behaviour and it look likes all Android apps made by PCSoft are not stable. For me the crash is reproducable and consequent.
We developed first on 22, but after this problem, we recompiled the same apps to version 23, but no success or change in behaviour.
Reproduction is very consequent:
• Launch WDM app and fully initialize it.
• Start different apps like Mail, Word, Excel, Photo’s, Dropbox, OneDrive, Google Maps and use them for a short while. Approx 10 applications are open;
• Lock phone and wait for about 5 to 10 min.
• Unlock Phone
• Select WDM App via “The Application Key” of the phone (That is the list with the most recently used menu items and applications);
• Crash
Hope someone knows this problem.
After using the app, using other apps and reactivate the app again, we get a popup from Android with the info that the Application is stopped and we get an error like:
Quote
===== Error =====
Date and time=18/02/2019 16:57:08
Message=View with id -1: fr.pcsoft.wdjava.ui.champs.fenetreinterne.u#onMeasure() did not set the measured dimension by calling setMeasuredDimension()
Java stack=android.view.View.measure(View.java:23309)
android.view.ViewGroup.measureChild(ViewGroup.java:6899)
android.view.ViewGroup.measureChildren(ViewGroup.java:6876)
android.widget.AbsoluteLayout.onMeasure(AbsoluteLayout.java:66)
android.view.View.measure(View.java:23297)
android.view.ViewGroup.measureChild(ViewGroup.java:6899)
android.view.ViewGroup.measureChildren(ViewGroup.java:6876)
android.widget.AbsoluteLayout.onMeasure(AbsoluteLayout.java:66)
android.view.View.measure(View.java:23297)
android.view.ViewGroup.measureChild(ViewGroup.java:6899)
android.view.ViewGroup.measureChildren(ViewGroup.java:6876)
fr.pcsoft.wdjava.ui.champs.fenetre.m.onMeasure(Unknown Source:9)
android.view.View.measure(View.java:23297)
android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6928)
android.widget.FrameLayout.onMeasure(FrameLayout.java:185)
android.view.View.measure(View.java:23297)
android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6928)
android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1514)
android.widget.LinearLayout.measureVertical(LinearLayout.java:806)
android.widget.LinearLayout.onMeasure(LinearLayout.java:685)
android.view.View.measure(View.java:23297)
android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6928)
android.widget.FrameLayout.onMeasure(FrameLayout.java:185)
com.android.internal.policy.DecorView.onMeasure(DecorView.java:899)
android.view.View.measure(View.java:23297)
android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:2886)
android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1916)
android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2171)
android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1785)
android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7832)
android.view.Choreographer$CallbackRecord.run(Choreographer.java:911)
android.view.Choreographer.doCallbacks(Choreographer.java:723)
android.view.Choreographer.doFrame(Choreographer.java:658)
android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:897)
android.os.Handler.handleCallback(Handler.java:789)
android.os.Handler.dispatchMessage(Handler.java:98)
android.os.Looper.loop(Looper.java:164)
android.app.ActivityThread.main(ActivityThread.java:6944)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Thread=id=2
name=main
priority=5
groupName=main
===== Screen shot =====
Path=file:///storage/emulated/0/Android/data/com.zzz.xxx/cache/err1549987028651.png
===== Application =====
Application name=Xxx
Application version=1.0.14.0
Name of the package=com.zzz.xxx
Date and time of startup=18/02/2019 16:57:04
=22.0.279.0 (en)
===== Device =====
Model=SM-A520F
Constructor=samsung
Make=samsung
===== System =====
Version number of Android=8.0.0 (unknown)
Android Level Api=26
Total internal storage memory=23,58 GB
Internal storage memory available=14,63 GB
Screen density=480
Screen resolution=1080x1920
We tested on several Android Devices (Samsung S5 NEO, Samsung A5, Samsung A8 and Samsung S9) with several Windev Mobile apps.
The phones are provided with the (for them) latest OS.Even the apps from the examples and from the Google Store that are published by PCSoft give this kind of behaviour and it look likes all Android apps made by PCSoft are not stable. For me the crash is reproducable and consequent.
We developed first on 22, but after this problem, we recompiled the same apps to version 23, but no success or change in behaviour.
Reproduction is very consequent:
• Launch WDM app and fully initialize it.
• Start different apps like Mail, Word, Excel, Photo’s, Dropbox, OneDrive, Google Maps and use them for a short while. Approx 10 applications are open;
• Lock phone and wait for about 5 to 10 min.
• Unlock Phone
• Select WDM App via “The Application Key” of the phone (That is the list with the most recently used menu items and applications);
• Crash
Hope someone knows this problem.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable February 20, 2019 05:53PM |
Admin Registered: 5 years ago Posts: 19 |
Hi William,
sorry to hear, as soon I've read that, I looked in my emails, but found no mails like this?!
this error I got in the last year about 12 times: (WD22 & WD23, Android 6,7,8,8.1)
===== Error =====
Date and time=18/02/2019 19:55:57
Message=Unable to create <!s!> file.
File found neither on disk, nor in libraries (.WDL) or components (.WDK).
System Message=What happened?
Unable to create <!s!> file.
File found neither on disk, nor in libraries (.WDL) or components (.WDK).
Error code: !d!
Level: fatal error
WD55 error code: !d!
System error code: !d!
System error message:
No such file or directory
Dump of the error of 'module ( ).
Debugging information:
##(IXStream)-Handle=<0xffffffff>##
Additional Information:
EIT_SRCFILE : </storage/emulated/0/NabooDVD/studio.ndx>
EIT_LOGICALTABLENAME : <studio>
EIT_DATAACCESS : <0xd74fe880>
Code=70302
WLanguage function=HCreationIfNotFound
Process=Initializing Naboo DVD
WLanguage stack=Initializing Naboo DVD
Java stack=fr.pcsoft.wdjava.core.erreur.WDErreurManager.a(Unknown Source:22)
fr.pcsoft.wdjava.database.hf.WDHF_Manager.a(Unknown Source:37)
fr.pcsoft.wdjava.database.hf.k.a(Unknown Source:44)
fr.pcsoft.wdjava.database.hf.WDHF_Manager.c(Unknown Source:43)
fr.pcsoft.wdjava.api.WDAPIHF.hCreationSiInexistant(Unknown Source:13)
fr.pcsoft.wdjava.api.WDAPIHF.hCreationSiInexistant(Unknown Source:2)
cc.predl.dvd.wdgen.GWDPNaboo_DVD.initProjet(GWDPNaboo_DVD.java:366)
fr.pcsoft.wdjava.core.application.WDProjet.demarrer(Unknown Source:42)
fr.pcsoft.wdjava.core.application.l.a(Unknown Source:10)
fr.pcsoft.wdjava.core.application.l.doInBackground(Unknown Source:0)
android.os.AsyncTask$2.call(AsyncTask.java:333)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
java.lang.Thread.run(Thread.java:764)
Thread=id=2191
name=AsyncTask #1
priority=5
groupName=main
===== Screen shot =====
Path=file:///storage/emulated/0/Android/data/cc.predl.dvd/cache/err1550516157839.png
===== Application =====
Application name=Naboo DVD
Application version=3.0.0.0
Name of the package=cc.predl.dvd
Date and time of startup=18/02/2019 19:55:57
Version of Android framework=23.0.227.0 (en)
===== Device =====
Model=SM-A530F
Constructor=samsung
Make=samsung
===== System =====
Version number of Android=8.0.0 (O)
Android Level Api=26
Total internal storage memory=24,21 GB
Internal storage memory available=11,03 GB
Screen density=480
Screen resolution=1080x2220
but nothing else...
I tried your reproducing steps... but nothing, maybe you working with a incompatible app? Word, Excel?
I tried with:
TomTom
Google Maps
Camera
Gallery
Calling
Facebook Messenger
WhatsApp
Messages
10? Apps? I need to open 10 Apps additionally or only they are "open" because they run in background and you opened another 2-3 apps and worked with them?
Then Lock, waited 10 Minutes and more...
Unlock
Open "Task Manager", select my app
Works.. no crash...
sorry to hear, as soon I've read that, I looked in my emails, but found no mails like this?!
this error I got in the last year about 12 times: (WD22 & WD23, Android 6,7,8,8.1)
===== Error =====
Date and time=18/02/2019 19:55:57
Message=Unable to create <!s!> file.
File found neither on disk, nor in libraries (.WDL) or components (.WDK).
System Message=What happened?
Unable to create <!s!> file.
File found neither on disk, nor in libraries (.WDL) or components (.WDK).
Error code: !d!
Level: fatal error
WD55 error code: !d!
System error code: !d!
System error message:
No such file or directory
Dump of the error of 'module ( ).
Debugging information:
##(IXStream)-Handle=<0xffffffff>##
Additional Information:
EIT_SRCFILE : </storage/emulated/0/NabooDVD/studio.ndx>
EIT_LOGICALTABLENAME : <studio>
EIT_DATAACCESS : <0xd74fe880>
Code=70302
WLanguage function=HCreationIfNotFound
Process=Initializing Naboo DVD
WLanguage stack=Initializing Naboo DVD
Java stack=fr.pcsoft.wdjava.core.erreur.WDErreurManager.a(Unknown Source:22)
fr.pcsoft.wdjava.database.hf.WDHF_Manager.a(Unknown Source:37)
fr.pcsoft.wdjava.database.hf.k.a(Unknown Source:44)
fr.pcsoft.wdjava.database.hf.WDHF_Manager.c(Unknown Source:43)
fr.pcsoft.wdjava.api.WDAPIHF.hCreationSiInexistant(Unknown Source:13)
fr.pcsoft.wdjava.api.WDAPIHF.hCreationSiInexistant(Unknown Source:2)
cc.predl.dvd.wdgen.GWDPNaboo_DVD.initProjet(GWDPNaboo_DVD.java:366)
fr.pcsoft.wdjava.core.application.WDProjet.demarrer(Unknown Source:42)
fr.pcsoft.wdjava.core.application.l.a(Unknown Source:10)
fr.pcsoft.wdjava.core.application.l.doInBackground(Unknown Source:0)
android.os.AsyncTask$2.call(AsyncTask.java:333)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
java.lang.Thread.run(Thread.java:764)
Thread=id=2191
name=AsyncTask #1
priority=5
groupName=main
===== Screen shot =====
Path=file:///storage/emulated/0/Android/data/cc.predl.dvd/cache/err1550516157839.png
===== Application =====
Application name=Naboo DVD
Application version=3.0.0.0
Name of the package=cc.predl.dvd
Date and time of startup=18/02/2019 19:55:57
Version of Android framework=23.0.227.0 (en)
===== Device =====
Model=SM-A530F
Constructor=samsung
Make=samsung
===== System =====
Version number of Android=8.0.0 (O)
Android Level Api=26
Total internal storage memory=24,21 GB
Internal storage memory available=11,03 GB
Screen density=480
Screen resolution=1080x2220
but nothing else...
I tried your reproducing steps... but nothing, maybe you working with a incompatible app? Word, Excel?
I tried with:
TomTom
Google Maps
Camera
Gallery
Calling
Facebook Messenger
Messages
10? Apps? I need to open 10 Apps additionally or only they are "open" because they run in background and you opened another 2-3 apps and worked with them?
Then Lock, waited 10 Minutes and more...
Unlock
Open "Task Manager", select my app
Works.. no crash...
|
Re: [WDM] All Android Apps are not stable. Crash reproducable February 21, 2019 03:17PM |
Registered: 5 years ago Posts: 3 |
Hi Guenter,
Thank you for your time. We investigated further and we noticed that apps without an Internal Window will give the same behavior, but the crash is less often reproducible.
We made a simple “Hello World” app and made a video to show the error. What we see is that activating the app from the background shows us that is goes immediately to the background (crash). And when you activate the app then the app starts over.
Of course the speed of opening apps in the 'operational' situation is slower and less often, but the behavior and response is the same as it happens on client phones.
The link to the video is: [youtu.be]
I am preparing a video with crash information, it will follow soon.
Kind regard,
William
Edited 1 time(s). Last edit at 02/21/2019 03:18PM by wilr.
Thank you for your time. We investigated further and we noticed that apps without an Internal Window will give the same behavior, but the crash is less often reproducible.
We made a simple “Hello World” app and made a video to show the error. What we see is that activating the app from the background shows us that is goes immediately to the background (crash). And when you activate the app then the app starts over.
Of course the speed of opening apps in the 'operational' situation is slower and less often, but the behavior and response is the same as it happens on client phones.
The link to the video is: [youtu.be]
I am preparing a video with crash information, it will follow soon.
Kind regard,
William
Edited 1 time(s). Last edit at 02/21/2019 03:18PM by wilr.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable March 11, 2019 09:01AM |
Registered: 5 years ago Posts: 12 |
We send 2 test apps to PCSoft to demonstrate the problem. Both test apps have 2 internal windows. The difference between the test apps is adding an image control.
In the test app without image control we only experience a restart of the application. The test app containing the image control crashes where there is either no error stack or there is, but not referring to the code.
Based on our test procedure we were able to reproduce 8 out of 10 times.
We tested in WDM22 and WDM23. In the PCSoft forum another user reported the same problem in WDM24.
This is a serious show stopper for developing apps with Windev Mobile.
In the test app without image control we only experience a restart of the application. The test app containing the image control crashes where there is either no error stack or there is, but not referring to the code.
Based on our test procedure we were able to reproduce 8 out of 10 times.
We tested in WDM22 and WDM23. In the PCSoft forum another user reported the same problem in WDM24.
This is a serious show stopper for developing apps with Windev Mobile.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable March 12, 2019 10:16PM |
Registered: 5 years ago Posts: 73 |
|
Re: [WDM] All Android Apps are not stable. Crash reproducable March 13, 2019 04:43PM |
Registered: 5 years ago Posts: 3 |
Hi ISO,
Thank you for your help.
Please allow me to share two APK files.
[www.dropbox.com]
[www.dropbox.com]
Testapp 12
Achitecture
• Main window contains 2 IW controls
• IW_Login with login button
• IW_Work
• When app is running plane with login is displayed.
• Click login button and plane with work is appeared.
Behaviour
• shows after our test procedures (see below) a black screen, app starts and closes.
• The same behavior we get when we do this on the ‘WMSports’ app from the Appstore.
Testapp 13
Achitecture
• Main window contains 2 IW controls
• IW_Login with login button and IMAGE control;
• IW_Work
• When app is running plane with login is displayed.
• Click login button and plane with work is appeared.
Behaviour
• Testapp 13 shows after reactivating the popup "Test App 13 has stopped”.
• We are not able see a stack.
This crash occurs at least 8 of the 10 times when testing the 2 different applications. Other applications from other manufactures don’t have those problems.
Testing Procedures
• Install concerned app.
• Close all other apps through the task list.
• Start the concerned app and let it fully load up.
• Click on Login, so IW_Work appears
• Go back to the home screen.
• Start-up different apps.
• Let these apps fully load up
• Use them if necessary
• The app threshold lays around 15 to 20 apps.
• Start the concerned app again.
• Through the task list or by tapping the icon
• Crash.
• After restart IW_Login is shown
This threshold is quite high, but this is depending on the memory use of the other apps. To force the behavior, use a benchmarking tool if the crash doesn’t happen, to allocate more resources and to simulate heavy workloads that may occur on work related phones.
Thank you for your help.
Please allow me to share two APK files.
[www.dropbox.com]
[www.dropbox.com]
Testapp 12
Achitecture
• Main window contains 2 IW controls
• IW_Login with login button
• IW_Work
• When app is running plane with login is displayed.
• Click login button and plane with work is appeared.
Behaviour
• shows after our test procedures (see below) a black screen, app starts and closes.
• The same behavior we get when we do this on the ‘WMSports’ app from the Appstore.
Testapp 13
Achitecture
• Main window contains 2 IW controls
• IW_Login with login button and IMAGE control;
• IW_Work
• When app is running plane with login is displayed.
• Click login button and plane with work is appeared.
Behaviour
• Testapp 13 shows after reactivating the popup "Test App 13 has stopped”.
• We are not able see a stack.
This crash occurs at least 8 of the 10 times when testing the 2 different applications. Other applications from other manufactures don’t have those problems.
Testing Procedures
• Install concerned app.
• Close all other apps through the task list.
• Start the concerned app and let it fully load up.
• Click on Login, so IW_Work appears
• Go back to the home screen.
• Start-up different apps.
• Let these apps fully load up
• Use them if necessary
• The app threshold lays around 15 to 20 apps.
• Start the concerned app again.
• Through the task list or by tapping the icon
• Crash.
• After restart IW_Login is shown
This threshold is quite high, but this is depending on the memory use of the other apps. To force the behavior, use a benchmarking tool if the crash doesn’t happen, to allocate more resources and to simulate heavy workloads that may occur on work related phones.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable March 15, 2019 10:15PM |
Registered: 5 years ago Posts: 79 |
Hi. I've tested an app that uses a lot of windows, quite a few of them internal. The device runs Android 9 and has 3 GB of RAM (Xiaomi A1). My experience opening several apps and reselecting them from "Recent Applications" has been:
1) My app doesn't show errors when selecting it again, but it is true that the app loads again (splash window, etc).
2) That same behavior has seen them reopen several of the apps I had used in the test, including Google applications. Other apps like Play Store open just as they were when you put it in the background.
I think this needs to be tested further.
Ruben
1) My app doesn't show errors when selecting it again, but it is true that the app loads again (splash window, etc).
2) That same behavior has seen them reopen several of the apps I had used in the test, including Google applications. Other apps like Play Store open just as they were when you put it in the background.
I think this needs to be tested further.
Ruben
|
Re: [WDM] All Android Apps are not stable. Crash reproducable March 15, 2019 10:31PM |
Registered: 5 years ago Posts: 73 |
Hi
I installed the 1st apk, left it running in the background with a number of other apps also running including a windev app I have created which uses a lot of memory. Your app didn't crash and seemed fine when it was reopened. Could it just be a case of clashing with a specific app you have installed?
I'll try the 2nd apk when I get a bit of time.
I installed the 1st apk, left it running in the background with a number of other apps also running including a windev app I have created which uses a lot of memory. Your app didn't crash and seemed fine when it was reopened. Could it just be a case of clashing with a specific app you have installed?
I'll try the 2nd apk when I get a bit of time.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 16, 2019 06:02PM |
Registered: 5 years ago Posts: 79 |
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 18, 2019 08:20PM |
Registered: 5 years ago Posts: 12 |
For everybody experiencing these crashes, PCSoft finally recognized the error and produced a correction patch. This solved our crashes. It didn't solve the closing of the app in the background but probably this is due to Android behavior.
In the end we are happy that PCSoft solved the problem but getting there is as painful as always. In all our bug reports to PCSoft we have the same experience. We know we need to be very, very clear in communication and create a simple app to reproduce. The problem is that PCSoft's default reponse is performing a quick scan, not finding the issue and return the problem to us. And in almost every case we need to get angry before they investigate the problem seriously. For the record, all our reported problems ended in a correction patch. We really think PCSoft should improve this process.
Edited 1 time(s). Last edit at 04/18/2019 08:46PM by Adri.
In the end we are happy that PCSoft solved the problem but getting there is as painful as always. In all our bug reports to PCSoft we have the same experience. We know we need to be very, very clear in communication and create a simple app to reproduce. The problem is that PCSoft's default reponse is performing a quick scan, not finding the issue and return the problem to us. And in almost every case we need to get angry before they investigate the problem seriously. For the record, all our reported problems ended in a correction patch. We really think PCSoft should improve this process.
Edited 1 time(s). Last edit at 04/18/2019 08:46PM by Adri.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 18, 2019 11:51PM |
Registered: 5 years ago Posts: 79 |
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 19, 2019 09:14PM |
Registered: 5 years ago Posts: 12 |
Hi Rubén,
I think you can ask PCSOFT for the download link. I do have it but I'm not sure I can post it.
See below for the PCSOFT response. It refers to a patch for WDM24. A patch for WDM23 is also available.
Cheers,
Adri
A fix is available for the incident #111194 regarding closing an application in the background.
Use this link to download the upgrade for WinDev Mobile 24 version interne 240042H:
#########
This upgrade includes:
- \framework\android\dep\depfmk.fic (581,71 Ko)
- \framework\android\dep\depfmk.mmo (1057,33 Ko)
- \framework\android\dep\depfmk.ndx (2100,49 Ko)
- \framework\android\dep\external.fic (3,59 Ko)
- \framework\android\dep\external.mmo (22,96 Ko)
- \framework\android\dep\external.ndx (2,60 Ko)
- \framework\android\dep\prg.dat (72,00 Ko)
- \framework\android\us\wd240android.jar (5833,66 Ko)
Unzip it keeping the tree structure in the \Programs\ folder of WinDev Mobile 24.
After that recreate the APK application of the project, in order to deploy it again on the Android device or publish it in the Store.
Edited 1 time(s). Last edit at 04/19/2019 09:18PM by Adri.
I think you can ask PCSOFT for the download link. I do have it but I'm not sure I can post it.
See below for the PCSOFT response. It refers to a patch for WDM24. A patch for WDM23 is also available.
Cheers,
Adri
A fix is available for the incident #111194 regarding closing an application in the background.
Use this link to download the upgrade for WinDev Mobile 24 version interne 240042H:
#########
This upgrade includes:
- \framework\android\dep\depfmk.fic (581,71 Ko)
- \framework\android\dep\depfmk.mmo (1057,33 Ko)
- \framework\android\dep\depfmk.ndx (2100,49 Ko)
- \framework\android\dep\external.fic (3,59 Ko)
- \framework\android\dep\external.mmo (22,96 Ko)
- \framework\android\dep\external.ndx (2,60 Ko)
- \framework\android\dep\prg.dat (72,00 Ko)
- \framework\android\us\wd240android.jar (5833,66 Ko)
Unzip it keeping the tree structure in the \Programs\ folder of WinDev Mobile 24.
After that recreate the APK application of the project, in order to deploy it again on the Android device or publish it in the Store.
Edited 1 time(s). Last edit at 04/19/2019 09:18PM by Adri.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 21, 2019 12:44AM |
Registered: 5 years ago Posts: 79 |
Hi. The patch is for 240042H internal version. Have you tried the latest published version 63m to see if the error is corrected in it?
For me the last version 63m is less stable than the prerelease 54v... The application closes frequently but does not generate framework error as before.
Thank you
Rubén
Edited 1 time(s). Last edit at 04/21/2019 12:48AM by Rubén Sánchez.
For me the last version 63m is less stable than the prerelease 54v... The application closes frequently but does not generate framework error as before.
Thank you
Rubén
Edited 1 time(s). Last edit at 04/21/2019 12:48AM by Rubén Sánchez.
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 23, 2019 07:30AM |
Registered: 5 years ago Posts: 12 |
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 24, 2019 06:44AM |
Registered: 5 years ago Posts: 151 |
|
Re: [WDM] All Android Apps are not stable. Crash reproducable April 24, 2019 07:32AM |
Registered: 5 years ago Posts: 12 |
