Skip to content
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

[Maps] Cloud issue with Tile Map Service from URL option #29863

Closed
alexfrancoeur opened this issue Feb 1, 2019 · 2 comments · Fixed by #30327
Closed

[Maps] Cloud issue with Tile Map Service from URL option #29863

alexfrancoeur opened this issue Feb 1, 2019 · 2 comments · Fixed by #30327
Assignees
Labels
blocker bug Fixes for quality problems that affect the customer experience [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation v6.7.0 v7.0.0

Comments

@alexfrancoeur
Copy link

I used an incorrect and http tile map service and am now consistently seeing this error on 6.7 cloud staging. Can anyone on the @elastic/kibana-gis reproduce?

52146856-058fab80-2633-11e9-9ba8-4a9608562c3b

@alexfrancoeur alexfrancoeur added bug Fixes for quality problems that affect the customer experience [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation labels Feb 1, 2019
@alexfrancoeur alexfrancoeur changed the title Cloud issue with Tile Map Service from URL option [Maps] Cloud issue with Tile Map Service from URL option Feb 1, 2019
@thomasneirynck
Copy link
Contributor

this may or may not be cloud. there's another bug related to tilemaps.

cf. #29733

@taku333
Copy link
Contributor

taku333 commented Feb 4, 2019

I also encountered a similar error.
Kibana: ver.7.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker bug Fixes for quality problems that affect the customer experience [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation v6.7.0 v7.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants