IoT Creators Bug Tracker 🐞
-
Hi all,
we know that bugs are frustrating, but let’s keep track on them together so we can fix them ASAP. If you encounter any other problems, please let us know here.
These are the bugs that we are aware of and working on
PORTAL
Search device by IMEI not functional(28.05 fixed with limitation; 02.06 fully fixed)Device overview not consistent (i.e., empty pages)(28.05 fixed for most cases)Broken Link to edit billing address in invoice overview(02.06 fixed)Confusing 404 wording(fixed)Adding devices in project results in error message and site needs to reload in order to see all devices(Hotfix deployed: 31.05)Refresh Table link on the portal does not work(02.06 fixed)Minor issues with the CSV import
DOCUMENTATIONPage https://docs.iotcreators.com/docs/sim-cards has a link leading to https://forum.iot.t-mobile.nl/(28.05. URL fixed with newest version)
Florian
-
Portal
- Billing address “edit” not functional
-
Hi magnatron,
thanks for reporting. I can not reproduce the bug. Can you please give more details.
Thanks
-
- Log in
- Click on INVOICES in the left menu
- Click on “Edit” beneath your “Billing address”
- Witness a creative 404 page
-
404 page
- incorrect spelling “We could not found what you are looking for”
- What is “the homepage” in “Try again from the homepage” and why is there a button “Go to your dashboard” if I should try from the homepage?
(as in “who is General Failure and why is he reading my drive?”)
-
Thanks. I put this to the list of errors and created some backlog tickets for our developers. In case you need to change your billing address at the moment, you still should be able to do this in the setting view.
-
Broken link(s?)
- Link(s) in the docs is (are?) broken.
E.g: Page https://docs.iotcreators.com/docs/sim-cards has a link leading to https://forum.iot.t-mobile.nl/ (which has no valid SSL)
- Link(s) in the docs is (are?) broken.
-
Missing info about Chip-SIM
https://docs.iotcreators.com/docs/sim-cards doesn’t seem to have any info on the newest kid on the block…
-
This post is deleted! -
This post is deleted! -
Registering device via portal is defunct
URGENT!!
Also registering via the portal does not work and results in error messages:
-
@magnatron This happened to me as well, but after refreshing the page I found out that the device did actually register. It just gave these error messages.
-
@Cees-Meijer “This” as in using the portal or the API?
-
@magnatron In the portal.
-
@Cees-Meijer I’m trying now but I do not see the device after refresh. The portal might use a shadow-API but the actual API is much more important to us as we use that for our devices in our production flow.
-
The portal does work now and then. Another device did register even after the error messages as you said. Thanks for the tip!
-
@magnatron Please check: https://docs.iotcreators.com/docs/sim-cards - it has information about eSIM and nuSIM. Last week this link lead another old version without these information and old links. This should now be fixed. Maybe you need to clear your cache.
-
@Florian-Duecker
It is probably the same looking at the “MFF2” tag, but i’m drowning in abbreviations already, so please can you confirm if the “eSIM” on that page is the same as the offered “Chip-Sim” on the SIM order page? -
Small bug (which I already reported two weeks ago, so it’s not related to the upgrade) : The ‘Refresh Table’ link on the portal does not work. I already tried different browsers, but no result.
-
@Cees-Meijer Thanks. I added this to the list and our backlog.
@magnatron regarding the communication of the change: I’m sorry you missed that. I will try to make it more prominent next time, but please also check your emails from 24.04 and 19.05 where we also made aware of this. Regarding the SIM: From my understanding: MFF2 is the form factor. eSIM stands for embedded SIM and this could be done in different form factors (e.g., MFF2, WLCSP). But the MFF2 SIM is an eSIM. It needs to be soldered on. I’m not an expert on this and would ask to bring this topic to another thread if necessary as I don’t consider this as bug. thanks!
