Closed artwist-polyakov closed 3 weeks ago
*🆕 Untriaged**
The team has not yet reviewed the issue. We usually do it within one business day. Docs: https://github.com/toeverything/AFFiNE/blob/canary/docs/issue-triaging.md
This is an automatic reply by the bot.
instead of the JS and CSS code, an error page is returned: https://docs.polyakov.marketing/js/runtime.3b180e24.js https://docs.polyakov.marketing/vendor.4b03f911.css and this is the case for all mobile version resources. For comparison, the desktop script: https://docs.polyakov.marketing/js/runtime.a8387fa9.js
Most likely, the problem is with the engine, since the URLs are fundamentally the same, i.e., nginx serves them from the same place, and the issue is that the mobile ones are somehow not there. Or it could be something related to access rights.
instead of the JS and CSS code, an error page is returned: https://docs.polyakov.marketing/js/runtime.3b180e24.js https://docs.polyakov.marketing/vendor.4b03f911.css and this is the case for all mobile version resources. For comparison, the desktop script: https://docs.polyakov.marketing/js/runtime.a8387fa9.js
Most likely, the problem is with the engine, since the URLs are fundamentally the same, i.e., nginx serves them from the same place, and the issue is that the mobile ones are somehow not there. Or it could be something related to access rights.
Hello, how is this problem solved?
instead of the JS and CSS code, an error page is returned: https://docs.polyakov.marketing/js/runtime.3b180e24.js https://docs.polyakov.marketing/vendor.4b03f911.css and this is the case for all mobile version resources. For comparison, the desktop script: https://docs.polyakov.marketing/js/runtime.a8387fa9.js Most likely, the problem is with the engine, since the URLs are fundamentally the same, i.e., nginx serves them from the same place, and the issue is that the mobile ones are somehow not there. Or it could be something related to access rights.
Hello, how is this problem solved?
It isn't solved.
@forehalo hello, problem still be represented after update to last stable. Why do you close this issue?
@forehalo hello, problem still be represented after update to last stable. Why do you close this issue?
It's fixed but not yet released in stable. Once linked PR is merged to the main branch, GitHub will automatically close the issue for you.
That's how GitHub works.
For the stable releases: For a version X.Y.Z: When X, Y increases, the release will include all the main branch commits in the normal case. When Z increases, only those urgent bug fixes will be included.
@fourdim Got it! Still waiting next stable)
@fourdim hello, i've just update version to last stable, and bug with mobile version of pages still being represented
@fourdim hello, i've just update version to last stable, and bug with mobile version of pages still being represented
0.17.5 is still a patch release 0.18.0
I tried to use the beta version of 0.18.0. I can view the link, but it requires to login. Use firefox will be OK for mobile view.
What happened?
On mobile browsers, when attempting to open shared notes, a blank screen is displayed.
Steps to Reproduce:
Additional Information:
logs in console:
large screenshot from iPhone
on desktops:
Distribution version
Web (app.affine.pro)
What browsers are you seeing the problem on if you're using web version?
Chrome
Are you self-hosting?
Relevant log output
No response
Anything else?
No response