@nathanaelb Sure have. Both on and off (auto-record)
Same Results
1 Like
Different browsers, devices, plans, settings.
What have we not tried?
Are the OS’s up to date?
Yeah driving me mad now (well not mad but getting increasingly frustrated)
oS’s up to date.
Dunno 
what else to try.
I wish there was more support or explanation around the error rather than the message I get which is pretty generic - failed.
Appreciate your input so far.
I won’t be giving up
Your troubles are making me question what I built. It’s in production for a client and to be used starting next week by 20-30 people for starters. It works perfectly. For now.
I wish we could figure out your issue: it would be good for you, others who want to use the action and me so I can rest assured the action actually works.
1 Like
Morning, Jason 
Any luck?
1 Like
Morning, nope 
I even borrowed an Android device to test ( as opposed to my Apple gear) and it didn’t work.
I hope your project went ok. I know you were a little nervous with 20-30 users using this feature.
Don’t know what to do next. Think I have given up
Never give up. Never surrender.
1 Like
Do you have a team in your account you could invite me to as a member?
Thanks
Sure 
Send me a message with your email.
Appreciate it
I send you a message with my email.
1 Like
So I accessed your app and tested on an Android phone only:
- Tested the voice feature you built in the builder: it worked
- Tested the voice feature you built on my phone: error
- Set the app to private.
- Built a voice feature by writing the transcript to the users table.
- Tested the voice feature I built on my phone: it worked
- Tested the voice feature you built on my phone: it worked
- I set the access settings back to public with no user profile needed, reloaded the app on my phone, tested both of our features: error
- I set the access settings back to private, reloaded the app on my phone, tested both of our features: it worked
The error would be related to the access settings of the app? When the access is set to private, the Voice & Transcribe action seems to work well.
3 Likes
Aside from testing the Record & Transcribe, I wonder what the difference between testing in the builder and testing in an app in production. There seems to be a difference.
Question about the Record & Transcribe Voice action.
When access to the app is set to private in settings, the Voice & Transcribe action seems to work well. When access is set to public with no user profile needed, Voice & Transcribe action fails and returns an error.
Is this expected behavior?
1 Like
Appreciate the report. That should not be the case.
It always returns an error?
1 Like
I’ve been able to reproduce reliably in one account on the Free plan.
1 Like
To be clear, this is about an app being public and not a team on the Free plan, correct?
This is indeed about the app being public.
I specified the nature of the plan because the limited tests can’t exclude that other factors might explain the reason for error message.
It does appear through that the app being public reliably triggers the error message and thereby the inability to write the transcription to a table.
1 Like