-
-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android textField do not work #63
Comments
Is this still an issue, @NodeGIS? If yes, do you have an idea what might cause the problem? |
Same problem here. I've found that set the |
Hi, just found the same problem. I tried using the |
I encountered a similar issue myself. After investing hours into the problem, I discovered that it is tied to the source of your glyphs server in Maplibre. Maplibre does not default to using certain fonts; instead, it relies on the configuration specified in style.json. Consequently, it's crucial to ensure that your server can properly return the specified fonts. Failure to do so may result in an error message similar to the one below: The error message associated with this issue might look like:
If the server cannot return the written type. To address this, it's essential to ensure that your server can successfully return the multiple fonts, preventing HTTP status code 403 errors. It would be nice if Maplibre would use a default for the text font, I don't think the current behavior is a bug but it's |
Thanks for sharing this @tvaknin! Isn't it using In any case, if someone wants to see this behavior changed, please open a new issue with the details. I agree that it doesn't look like a bug. |
@louwers Indeed there is a default but it's not clear that it relies on a map server to fetch the default one. |
Might be off-topic, but let me still mention that |
Migrating from MapBox to MapLibre, I found that SymbolLayer's PropertyFactory.textField(Expression.get("xxxx") does not work, if set prop for feature, the geomerty and label can not show!
My code as this:
The text was updated successfully, but these errors were encountered: