When I am downloading the report, it shows that “deviceid not found” even though I never had this issue before and the teams are still using the same device
@baretraq, these posts discussed previously should help you understand more about device id metadata:
And this post too …
And this one too …
Thank you, i read them all but i still don’t know how to fix it, i never changed any settings. @Kal_Lam
same problem here, I use deviceid to verify the user before allowing them to see the content of the form, but it’s not working anymore for online submission, only working with enketo app…
I used to collect deviceid online for years and had no such problem, this is the first time this happened.
@Kal_Lam I hope you give this some attention because it’s a new problem occured a couple of days ago.
@Sobaie_Mando, @baretraq seeing deviceid not found when collecting your data with Enketo is an expected behavior. It only works with the Collect Android App.
Actually, you should be getting a valid deviceid back for both KoboCollect and Enketo submissions. For KoboCollect it will be something along the lines of:
collect:lt8cEl43UgfwJX0P
which is a device-specific identifier. Whereas for Enketo, it will look like:
ee.kobotoolbox.org:Xh8fweaIiEgusYcZ
which is a browser-specific unique id that Enketo generates [so if you use a different browser on the same computer, you’ll actually end up with a different deviceid!].
This appears to be a recent regression and the Dev team is working on it.
Hi @Sobaie_Mando and @baretraq , thank you for reporting this. The solution has been deployed and you should now be able to see the device id without problem.

