none
Bing map V8 error "GetAllStopPoints" RRS feed

  • Question

  • Hi,

    We are getting below error while plotting the pushpin on map. This error encountered randomly not all time. This error is similar to "CurrentFramedata".

     Is any one encouterd below error and resolution for it.


    Balasaheb

    Monday, July 10, 2017 12:25 PM

Answers

  • Yes, you have reported this issue before. Can you provide more details, a code sample, which browser and browser version is being used, which country you are located in so that we can test under the same conditions. As noted before, we haven't been able to reproduce this issue and few have experienced this issue. Until we are able to reproduce it we can't fix it. 

    [Blog] [twitter] [LinkedIn]

    Tuesday, July 11, 2017 5:57 PM

All replies

  • Given the error i suspect that your code uses the getAllWaypoints function of the directions manager. Can you provide a code block of were this is being used or provide details. Is this being called right after calling calculate directions or in the directions updated event handler?

    [Blog] [twitter] [LinkedIn]

    Monday, July 10, 2017 2:38 PM
  • Hi Ricky,

    Thanks for your reply. We are plotting the pushpin on map not plot direction using direction manager. We will check more on this and let you know exactly when we are getting this error.

    Can you please check our below issues listed on following link and let us know your resposne for the same because this issues is very critical for us.

    https://social.msdn.microsoft.com/Forums/en-US/7cd7273c-9375-4163-a121-be541ddf3caa/svg-pushpin-position-issue?forum=bingmaps

    https://social.msdn.microsoft.com/Forums/en-US/a4d6731d-b262-441b-bf2c-7defbb435cfb/unable-to-get-property-currentframedata-error-in-bing-map-v8?forum=bingmaps

    Thanks!

     


    Balasaheb

    Tuesday, July 11, 2017 1:10 PM
  • Yes, you have reported this issue before. Can you provide more details, a code sample, which browser and browser version is being used, which country you are located in so that we can test under the same conditions. As noted before, we haven't been able to reproduce this issue and few have experienced this issue. Until we are able to reproduce it we can't fix it. 

    [Blog] [twitter] [LinkedIn]

    Tuesday, July 11, 2017 5:57 PM