1. What is the issue? Please be detailed.
When searching using the new AI Search in BOTH the "Ask AI" and the ordinary "Search" options, errors return with no results.
2. What steps can we take to reproduce this issue?
Go to ODK Docs using Chrome or Chrome Based Browsers and type something in the new Ask AI search box. You can navigate to the "Search" button to the right of "Ask AI" after searching to change the search type.
3. What have you tried to fix the issue?
I used Safari and everything works fine. Chrome and Brave Browsers are showing the behavior explained above.
4. Upload any forms or screenshots you can share publicly below.
This final Screenshot below is what comes up in Safari
I was not able to replicate this issue.
Tested using Chrome Version 138.0.7204.158 (Official Build) (arm64)
Is it still happening for you?
1 Like
I just checked on my Android using chrome and it works fine. On my Mac Mini 2023, running macOS 15.4.1 (24E263) it gives the following:
Using the following Brave Version:
Using Chrome Browser Version 138.0.7204.158 (Official Build) (arm64) gives this error:
It never asks for me to complete a reCAPTCHA or any kind of human confirmation test.
I've reached out to our friends at Kapa to see what has gone wrong. I'll update this topic once I know more...
It's working for me currently on an M1 Macbook Pro
Chrome Version 137.0.7151.69 (Official Build) (arm64)
Edge Version 137.0.3296.68 (Official build) (arm64)
Never experienced any such issues with ODK's AskAI so far, but I did experience the similar error messages with ChatGPT when I use it with VPNs / multi-layered privacy extensions (such as uBlock, FastForwarder, etc) and ad-blockers (or say whenever I try to hide my real presence, or surf the web anonymously).
Just a random guess - but I feel like it has something to do with browser's settings / installed extensions if any.
No VPNs here, but Brave browser is marketed as a chrome based but high privacy browser to limit google data mining. That wouldn't explain it not working in Chrome though. Brave and Chrome is still giving me the We noticed unusual activity. Please try asking your question again.
I rarely every use chrome and the only extension I have on is Google Docs Offline
Update: a couple minutes later and tried more questions and it works just fine in both Brave and Chrome...hmmm.
Glad to hear it's mostly working, @Tyler_Depke. If you run into the issue again, please share any error messages you’re seeing or details from your browser’s Network tab and Console.
1 Like
I’m still seeing the same error message pretty regularly. It most commonly gives this error
We noticed unusual activity. Please try asking your question again.
Internet has been pretty erratic lately and it often cuts out completely for a couple seconds. I got this error today and was getting the same errors last week also. I don’t know if any of the testing environments that allow you to throttle your internet speed actually let you do erratic things like completely cut your connection and then send it back up really fast. Downloading some large files earlier today I got speeds anywhere from bytes/s to nothing to 7MB/s (that usually lasts less than a second and immediately goes to a couple hundred KB/s). That being said, I’ve not run into a problem loading the actual websites on docs.getodk.org
I don’t know how detailed of logs you want from the browser, but I attached a .log file below. I had to change the extension to .txt to upload it on the forum as it wasn’t allowing me to upload .log files. This block seemed to repeat quite a bit:
sw.js:1 Error: [mobx-state-tree] You are trying to read or write to an object that is no longer part of a state tree. (Object type: 'AnonymousModel', Path upon death: '/tabStates/1256574743/injectionLifecycle/documents/D7E99786922B1BD1319309D2267E7BBF', Subpath: 'id', Action: ''). Either detach nodes first, or don't use objects after removing / replacing them in the tree.
at vf (sw.js:1:1017447)
at t.value (sw.js:1:989981)
at t.value (sw.js:1:992055)
at t.dehanceValue (sw.js:1:572904)
at t.get (sw.js:1:573434)
at e.getObservablePropValue_ (sw.js:1:606284)
at Object.get [as id] (sw.js:1:611070)
at e.get_ (sw.js:1:606851)
at Object.get (sw.js:1:590422)
at sw.js:1:589939
vf @ sw.js:1
docs.getodk.org-1754921455689.txt (35.8 KB)
1 Like
Thanks for the additional detail. I’ve sent it on to Kapa and I’ll report back what they say.
@Tyler_Depke, we've changed the bot detection mechanism and that should fix the problem. Let me know if you run into any other issues!
1 Like
