This video was sent to me by a user, and other users have also reported it… Basically the app doesn’t open and gives a memory error according to Playstore reports. I applied several recommendations that I found in this community but I haven’t managed to fix it yet. I would appreciate if you could help me find the solution, thank you very much in advance.
iTrade - Señales de trading para criptomonedas
iTrade es un proveedor de servicios de asesoramiento crítico y dirige a los comerciantes que quieren comerciar con criptodivisas.
iTrade (aplicación de Binance para señales criptográficas y comercio con Bitcoin) ofrece un eficiente servicio de investigación; y a través de él, nuestros hábiles y profesionales comerciantes le guiarán con la ayuda de un algoritmo verificado y propietario que proporciona información sobre el momento exacto de compra y venta de las criptodivisas más populares.
Serv...
Free
Attached are more details of the problem.
Interchange the mentioned above blocks.
You are closing the screen before opening the other screen which is incorrect
1 Like
Here in the community I found someone who said that this was the right way to switch between screens.
Taifun
July 15, 2020, 6:12pm
#5
this is the official solution
I see many issues done by users because they switched screens not correct.
This below is now just one of many other solutions:
[blocks]
If you dont open/close screens correct your app will get possible runtime errors.
Possible errors: (example)
Unable to add window -- token android.os.BinderProxy@45d459c0 is not valid; is your activity running?
Iam sure you don’t want that.
Then please do it in the future and switch screens correct.
General Tips and Tricks for App Inventor/Makeroid
…
Taifun
Cristopher_Toro:
Still not working : (
sorry for the audio, forget to mute the video xd
Taifun
July 15, 2020, 6:43pm
#8
you might want to check tip 2 here
Use different screens wisely
Before starting to create another screen, first you should think about is it really necessary? See also Building apps with many screens and SteveJG’s post about advantages/disadvantages , because in only one screen you also can use vertical arrangements to simulate different screens, just set the arrangements to visible = true/false as needed…
If you decided to use different screens, then you should switch them correctly, else you will run out of memory after a wh…
Taifun
compressed all project images and replaced them in kodular … still not working
vknow360
(Sunny Gupta)
July 16, 2020, 4:19am
#10
So do you want @Cristopher_Toro to open screen first and then close screen?
The blocks are correct as mentioned by @David
Maybe…but not the only solution.
These are also correct (in fact best):
2.
@Cristopher_Toro As the issue only occurs on Nougat and I have no nougat device so I can’t get the logcat.But still I shall try to produce issue on Lollipop.
Please post the logcat here if possible.
Thanks for replying, do some research on the logcats but I don’t know how to do it in my app … I am something new in this
ravigarg
(Ravi Garg)
July 16, 2020, 5:33am
#12
You can check this topic:
Name Of The App:
AISMCO
Download Link:
There are some crash reports in this app
The reports says 13 Crashes saying the following
[java.lang.OutOfMemoryError
in gnu.expr.PrimProcedure.apply]
Is there any way to solve the problem
1 Like
was the first to check, likewise thank you very much
Each of these vertical arrangements had a background image, so I have removed them. and it already opens the application, but now I have other errors.
works perfectly on my cell phone
ravigarg
(Ravi Garg)
July 16, 2020, 6:17am
#16
That can happen sometimes in companion if it is working in real device then I think your problem is solved.
1 Like
it is not companion, it is installed in the nox emulator
ravigarg
(Ravi Garg)
July 16, 2020, 6:47am
#18
Yea so it may be related to that if it is working fine in real device then most probably your problem is solved.
1 Like
Real device!
why they have changed the title of my post, in the description I have said that several users have reported that error to me, I also show a screenshot of the Google play console where you can see that the error not only happens to me using the emulator !! !!