Troubleshooting Common Issues
Last updated
Last updated
For those of you that have a Developer Account prior to setting up DIMO Global Accounts, here's a simple comparison between the console versions:
[Jan 2025] This is a known issue where a user is registered but failed to redirect to setting up your organization. We're working on a fix for this. In the meantime, if applicable, please use Google SSO instead.
This is likely due to some cookies stored in your browser's local storage. We recommend either clearing your browser cache or using a browser with incognito mode to continue with your access to the console.
[Jan 2025] For now, we recommend using Google Chrome to access the console. Alternatively, if you're using Brave Browser, we've seen success with users enabling certain settings.
To enable these, navigate to Brave > Settings > Extensions. From there, find the toggle called "Allow google login for extensions." Turn this setting ON, and restart your browser for the changes to take effect. Then, try logging into the console again.
You can read more about this setting here: https://github.com/brave/brave-browser/wiki/Allow-Google-login---Third-Parties-and-Extensions
Due to local restrictions, our current onramp provider might not support you paying with a credit card or a debit card. In cases like this, you can try the following:
Use a VPN, this will ask you for your address in the country you're tunneling to for validation.
Use your existing balances, this can be from your existing DIMO Account or from an external wallet of yours. For example, if you have DIMO or POL in an external wallet like MetaMask, you can simply send funds into your DIMO Account.
If none of the above works, you can reach out to our support for manual invoicing.
If you were charged, rest assure that your funds are secured in your account, it just likely never made it to DIMO or DCX.
Simply select the available fund balance and continue with your purchase.
$5 worth of DCX is required for a Developer License but the minimum DCX purchase is set at $10 to accommodate market fluctuations. So in the case where you need to use DIMO to get DCX, you will need at least $10 worth of DIMO in the current market price.
If you can't get payments to work or have any balance to transfer, you can reach out to our support for manual invoicing.
Always make sure you have enough DCX balance before creating your first app.
When creating your first app, it'll ask you for your project namespace. This is what your app will be identified as to the public, so this would be something like your company's name or your app name. For example: AAA or Driver Network.
The project namespace needs to be unique. If the namespace is used by another developer, you might experience an error here.
As of 2024, always select Production for your app.
Please self-identify first when you are running into this issue.
If you are an user registered in the old Developer Console prior to November 2024, reach out to support and let us know that you have an old license that needs clean up.
If you are a new user registering for the first time in the current Developer Console, reach out to support and let us know that you have problems with API key generation.
Please self-identify first when you are running into this issue.
If you are an user registered in the old Developer Console prior to November 2024, reach out to support and let us know that you have an old license that needs clean up.
If you are a new user registering for the first time in the current Developer Console, reach out to support and let us know that you have problems with Redirect URI configuration.
Yes, if you're interested in a more custom approach, follow the instructions under the Login with DIMO > Don't use React section.
The permissions template is a set of pre-defined SACD permissions that a developer may need. As of December 2024, we support two sets of permissions:
Permission Template 1- Every data permission
Permission Template 2- Every data permission except commands
To use the permission templates, simply feed in permissionTemplateId to the Login with DIMO component as input. An example might look like:
https://login.dimo.org/?clientId=<clientId>&redirectUri=<redirectUri>&permissionTemplateId=1&entryState=VEHICLE_MANAGER
This is a common issue for users who are using a plain NodeJS environment. For scalability of your backend code, we recommend using a strongly-typed TypeScript environment. For additional information on how to set up a Node project using TypeScript, follow this guide to get started.
access_token or developer_jwtPrevious versions of the SDK included a web3 dependency that contained breaking changes. As a first step, please ensure that you're on the latest version of the SDK: https://pypi.org/project/dimo-python-sdk/
You can use pip install dimo-python-sdk --upgrade to get the latest.
From there, make sure that you have a valid Developer License via the Dev Console, and that you're entering the correct values for your client_id, domain, and private_key.
The old console is setup where a user account can connect to different wallets which creates confusion down the road. The new console streamlines with and offer developers with an easier way to manage your license.
You can proceed to purchasing DCX again, but instead of paying with card, choose Pay with Balance this time around. You should see your full balance with spendable currencies listed as below:
