You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the filenames the users uploaded, it seems likely they're both using MacOS. The second user definitely is since the image path in their screenshot includes "Application Support". That might be some common ground worth investigating. I would've only tested MacOS on my dev machine. This could result in an imperfect test environment.
Worryingly, both users seem to have different paths that are not working. So this might be two separate issues! (On further inspection, the first user may have just intentionally cropped their home system path out of the screenshot)
The text was updated successfully, but these errors were encountered:
I've tried reproducing this in the dev environment and production on both MacOS and Windows across several versions of TwilioQuest with no luck. I'm wondering if this could be an issue with showdown? Based on this discussion, it makes me think the image path may be stirring things up because of the combined use of periods, dashes, and underscores. That being said, without a sure fire way to reproduce this it makes it hard to pinpoint the culprit.
Hey there, at the end of the Dark Ducktypium Forge challenge the image in the objective screen (of what I'm guessing is a map) doesn't seem to load. The path listed doesn't seem to exist - 
I'm not sure the root cause of this issue based on the reports. It does not seem to be happening to everyone.
There are two reports of this issue in Discord:
Based on the filenames the users uploaded, it seems likely they're both using MacOS. The second user definitely is since the image path in their screenshot includes "Application Support". That might be some common ground worth investigating. I would've only tested MacOS on my dev machine. This could result in an imperfect test environment.
Worryingly, both users seem to have different paths that are not working. So this might be two separate issues! (On further inspection, the first user may have just intentionally cropped their home system path out of the screenshot)
The text was updated successfully, but these errors were encountered: