-
Notifications
You must be signed in to change notification settings - Fork 112
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
[Bug]地图使用MapControl在iphone12 系统14.2.1上会报错 #532
Comments
Maybe because the iOS version (14.2.1) seems a bit too old. Google Maps API officially supported two major versions: iOS 16 and 17 so probably the latest library is not well tested on iOS 14. Browser Support | Maps JavaScript API | Google for Developers - https://developers.google.com/maps/documentation/javascript/browsersupport The latest version of iOS 14 is 14.8.1. I'm not sure if this can fix the issue but how about updating to the latest version of iOS 14. I don't recommend using iOS 14 though since it won't receive the security patch anymore. iOS version history - Wikipedia - https://en.wikipedia.org/wiki/IOS_version_history |
I think @shuuji3 is right: The stacktrace in your screenshot doesn't contain any stack frames from our library. I can only guess what that .close() method that causes the exception actually is, but it's probably part of a web-standard that isn't supported by older iOS versions. So there's probably nothing we could do about this. |
Another note: Please invest the time to translate a bug report into English, this will make it easier for us to understand and fix, and it will help others searching for similar issues find this. |
@usefulthink @shuuji3 Thanks to everyone, I have replaced the functional part I need without using mapControl. |
Description
Steps to Reproduce
It's just the normal official demo code, without any additional rendering, and then the above error is reported. Systems equal to or higher than iOS 15 will not have this error.
(original text)
就是正常的官方demo代码,没有其他渲染,然后就报上面的错误了。大于等于ios 15的系统都不会有这个报错。Environment
Logs
No response
The text was updated successfully, but these errors were encountered: