D2 heatmap breaks when match history was previously private

[CodyFitzpatrick]

I change my game history back and forth between private and public from time to time, and noticed the below when I went to check my heatmap today (yes, I am fortunate enough to be able to play a lot):

[CodyFitzpatrick]

The easy solution is to skip over data returned from the bungie API if it is error code 1665 or if there is no object returned and that object is not a string. Could be done via a simple "if" clause while populating the heatmap unless I'm missing something big.

[CodyFitzpatrick]

P.S. I'm not sure if the application is trying to store all history within a single variable, but for a guardian nearing 2000 hrs of playtime, I can't imagine it'd fare well!