vue nativescrript starter not working on samsung tab s7 fe

[sombriks]

Describe the bug

i am trying to create a nativescript vue project using my tablet but it's not working.
trying the same on mac/windows/linux works fine.

i am using google chrome on android and pc.

Link to the blitz that caused the error

https://stackblitz.com/edit/nativescript-stackblitz-templates-fndgxh?file=app%2Fcomponents%2FHome.vue&title=NativeScript%20Starter%20Vue

Steps to reproduce

see video
https://twitter.com/sombriks/status/1605331977745350656

Expected behavior

i want to use mobile to develop mobile

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

No response

Platform

Browser name  = Chrome
Full version  = 108.0.0.0
Major version = 108
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Linux; Android 12; SM-T735) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 84290969,
  "usedJSHeapSize": 66009733,
  "jsHeapSizeLimit": 1098907648
}
Hash = 6ebe18b1e1db1833797e3e4eb6ff802c375ee61b

Additional context

No response

[SamVerschueren]

Hi @sombriks, thanks for reporting. Does this only happen for the Vue Starter, or for every NativeScript project?

Would it be possible to get a screenshot of the Chrome Devtools on that device? It would really help if we know the exact error that's causing this. I can't seem to be able to reproduce in an Android Emulator, but an emulator is always a bit different so don't want to rely too much on that.

[sombriks]

Hello @SamVerschueren !

Here goes the screeshot from a nativescript-react starter:

It gets the same behavior seen in nativescrit-vue starter.

the vanilla js starter however behaves differently, it never ends the loading phase.

[sombriks]

that final prepeating warning is something like this:

The resource https://w-credentialless.staticblitz.com/yarn_index.6ebe18b1e1db1833797e3e4eb6ff802c375ee61b was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate as value and it is preloa

[fvsch]

Hi @sombriks. We could not reproduce on the Android devices we have so far.

The warning about preloaded resources should not be an issue. (It signals a performance optimization we might do on our side, but shouldn't affect you here.)

From the top of my mind, there are two things I'd like to check:

1. I'm seeing an entry in the Issues panel titled "Specify a Cross-Origin Resource Policy to prevent a resource from being blocked". Could you expand this issue and report back what resource(s) are being blocked?

2. To figure out if an issue might be caused by non-default browser settings or extensions, we usually want to test on the same machine with a blank Chrome profile. On desktop Chrome that's easy to do (you can start a Guest session), but on Android it's more limited. The best way to test with a brand new profile (outside of nuking all your settings and data in your main profile, which we don’t want) might be to download the Chrome Beta app from the Play Store, and use it without connecting a Google account or changing any settings. That would be testing Beta instead of the Stable release, but should probably be fine.

[sombriks]

Hello @fvsch !

I've followed your tip and tried native browser for this samsung tablet.

Turns out i do can use this android tablet to develop android via stackblitz and nativescript!

This is the screenshot when i inspect samsung browser instead of chrome:

Screenshot from device itself:

I can pair my phone with tablet via qr-code and see my app :-)

This is a game changer.

Regarding why chrome refuses to work properly i need more time to dig it up, but seeing it work properly with the out-of-the-box samsung browser solves my issue.

Thanks for the guidance and happy holidays!