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
Vuforia's result codes table spells this ``ProjectHasNoApiAccess``, while
this package mapped only ``ProjectHasNoAPIAccess``, a spelling which came
from a hand-written list in ``vws-python-mock`` rather than an observed
response. No real response with either casing has been found, so both
casings now map to ``ProjectHasNoAPIAccessError`` and the ambiguity is
recorded in the code.
``vws-python-mock`` 2026.8.14 changes the mock to the documented
spelling, so the pin is bumped to it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Map the ``ProjectHasNoApiAccess`` result code, as spelled in Vuforia's result codes table, to ``ProjectHasNoAPIAccessError``. The previously mapped ``ProjectHasNoAPIAccess`` casing still raises the same exception.
0 commit comments