You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've cloned the repo and the demo works in the dev tools (Wechat and QQ) and on my mobile device in the app (again, Wechat and QQ).
After running npm install and npm run build the demo continues to with in the dev tools but does not load on my mobile device, with no errors in the console or any feedback.
Perhaps you could remove package-lock.json from .gitignore so I can figure out the exact module versions you used.
Thanks!
The text was updated successfully, but these errors were encountered:
After running npm install and npm run build the demo continues to with in the dev tools but does not load on my mobile device, with no errors in the console or any feedback.
This is because pixi.js v5.3.0 has added BitmapFonts and used the XMLDocument, but the wechat environment does not support them, so I have updated @iro/wechat-adapter.
But this evaluates to false, even though the data has been successfully parsed and the next 2 conditions actually evaluate to true: data.getElementsByTagName('page').length && data.getElementsByTagName('info')[0].getAttribute('face') !== null;
If you want to use BitmapFonts in a Wechat or QQ environment, you may need to fully emulate the XMLDocument
implementation, which is a bit too much work.
In @iro/wechat-adapter I just defined XMLDocument so that the program doesn't report errors, use other ways instead of BitmapFonts would be a better choice.
I've cloned the repo and the demo works in the dev tools (Wechat and QQ) and on my mobile device in the app (again, Wechat and QQ).
After running
npm install
andnpm run build
the demo continues to with in the dev tools but does not load on my mobile device, with no errors in the console or any feedback.Perhaps you could remove
package-lock.json
from.gitignore
so I can figure out the exact module versions you used.Thanks!
The text was updated successfully, but these errors were encountered: