How to debug when my Ionic 4 app stop working? - ionic4

A bit of context (I have been stuck on this for a few days now):
The first screen on my Ionic 4 app is the login page. Once I logged in successfully, everything works fine. Then, when I log out & log back in, the app just hangs. There is no error showing up on the console. So, my question here is, how can I debug to find out what is causing the app to hang half way using it?
*It hangs in browser mode and when it is running on android.

In order to debug your app step by step I recommend using chrome developer tools.
First you will have access to your source code, therefore you can put breakpoints at any position you want.
You can open this window by inspecting your page and selecting the source tap.
To locate the problem you should have an idea about Ionic Page Life Cycle
,
If none of the above works you still have the possibility to console log the code that you want to verify, also the template can cause such an issue if you have for example an infinite *ngFor or something that prevent the template from loading.

Related

Cache Issues with Nuxt3 in Dev

i'm having trouble developing with Nuxt3, the problem is that sometimes edits in the code are not visible, it seems that Nitro caches something and I need to restart the server in order to see the updates. The most effective example is when I console.log something, then i remove the line, but the log still get printed after I reload the page. Any tips?

Chromium on startup behavior is different that launching it manually

I have a Jetson Nano that runs LXDE. After booting it should automatically start Chromium in kiosk mode and launch a web page. The web page is very simple, just adding and removing some rectangles or images based on web socket messages.
Since sometimes the DOM gets updated, sometimes not, I thought my web page has some bug. But this behavior is only on the Jetson Nano. Furthermore, when I launch the Chromium manually with the exact same parameters, I have no problem at all, everything runs as expected.
I also observed that the Chromium (the autostarted one) instantly updates the DOM correctly when I press Alt+Tab (since it is the only application, no application is really switched). So apparently nothing has happened since the last web socket message, I just press Alt+Tab, and the web page instantly is displaying the correct things. Additionally it is very difficult to bring up the developer console, pressing ctrl+shift+i for several minutes, when you are lucky it fires up the developer console. Once it is there, the web page is again working normally.
I have no idea what I can do about it. I just want to launch the Chrome so it behavior is like when I start it normally.
Currently, the autostart is done inside ~/.config/lxsession/LXDE/autostart with the line #/home/agx/dev/autostart/chromium.sh, this file is:
#!/bin/bash
sleep 60
chromium-browser --new-window --password-store=basic -kiosk --js-flags='--jitless' http://192.168.1.50/index.html
I tried to delay the start hoping it would help but it changed nothing. Same for jitless. I can execute exact this command manually in the console, chromium fires up and behaves normally.
How can I trace this one down?

infinite loop on consent screen login with google android ionic capacitor

I recently created an application with ionic capacitor, in it I use login with google, but I have the following drawback, on some phones (very few) it does not log, it stays on the consent screen, and when they press allow, it shows a loading and returns to leave the consent screen, over and over again, as in an infinite cycle, the thing is that I cannot replicate this on any device or emulator, it has happened on android 8 and 5.1, I even downloaded an emulator with android 5.1 and still I am not able to replicate the error, 90% of the users do manage to enter.
I do not know much about android, however I was reviewing the official documentation and it is identical to the implementation of the plugin (except for the calls to javascript after finishing), I thought it could be the configuration in the console, but I do not think, since as I said in 90% of the devices it works fine.
I would really appreciate if anyone could give me at least an idea on how to replicate the error, or something like that.
this is the plugin in question, in case it is of any use
https://github.com/CodetrixStudio/CapacitorGoogleAuth
I do not share code because I am sure that the problem is not in javascript
these are the scopes i'm using "profile", "email"

Route problem on production after build vue application

So, I'm building an application with Vuejs and after we finish her we decided to finally build for production. Everything worked just fine while building and etc, but when the application was really being hosted, we noticed some issues that we do not saw while on localhost (development and production).
I'm saying this after a lot of tests and researches about it because first, I thought that the problem was after building to production but we tested another way to host and it's not apache that is causing this issue and I really think that is not the code either. Anyway the problem is when we first access the application our login page is the first that you can see and it works just fine at the first access but if the user refreshes the page for any reason the page loses all her CSS because the route /auth/login goes to /auth/login/ and after some tests I can confirm. That bar that is added at the end of the route makes the page lose CSS.
This problem we solved by adding an exception on our .htaccess (we know that this is not that best practice but anyway) after this solved we saw another problem: when we click on a link for example /auth/login?token=12334567890 the token param simply disappear and the user is automatically redirected to /auth/login. So we think that maybe these two problems are related because when we first access and log in everything inside the application works as it should, these two problems are only occurring on our login component. My question is what is causing this problem only on this page? It's a vue-router that is causing?

iTunes Connect Missing Screenshot Error

I am trying to submit my app for review. I have included the screenshots for both iPhone 4 and iPhone 5. I however do not have a screenshot for the iPad as my app only runs on the iPhone. When trying to save, I keep on getting error "You must upload at least one screenshot". The screenshots I had selected then disappear from the selection. I use Firefox browser. Is there any reason for such an error? Please help.
As strange as it may sound, I used Firefox browser and then everything worked fine.