Feedback Case Number: N/A
I cant use feedback since it gives this error:
Reinstalled latest from xojo.com already, doesn’t make a difference.
Is there something we can do to report any case?
Does it work on another machine or in a VM on the same network?
It magically started to work suddenly…
Tried windows and had no issues there…
1 Like
Sorry again it’s not working anymore on MacOS
Can someone of the Xojo team tell me how i can get around this error?
If you run it from terminal does it give you any hints in the output?
And how should it be run from the terminal?
By the way i don’t have this issue on windows, only macOS.
-This issue is when opening feedback native on M1, if “Open with Rosetta” then it does run without issues…
Ok, so you have worked out the problem, or you still need help?
To open an app from Terminal type "open " and drag the app from Finder to Terminal.
Feedback starts fine on my M1 Mac. However, the app has the “Feedback has encountered an error” during start up shows up now and then.
That’s not a fix, that’s a workaround. Xojo is marketed as M1 Native… Feedback seems to be not…
I have no idea if Feedback has been compiled for M1 native yet, at least you know how to work around it until you find out.
Feedback starts fine on my M1 Mac. However, the app has the “Feedback has encountered an error” during start up shows up now and then.
i have the same as you can see in the screenshot above. It opens then shows a crash dialog and MUST quit… i can’t use it if it’s NOT running under rosetta…
The output of "open … " is 0-info…
Is this ^^ the output when a crash happens, or when it runs ok?
Opens, shows that dialog then i press Quit (on the dialog*) and i get 0-output.
- Otherwise i can’t continue, but after pressing it quits yes.
Ah how about if you run
/Applications/Feedback.app/Contents/MacOS/Feedback
from a terminal without using open (no idea if open changes the standard output, I’m not a mac person)
can’t …
more information required, I can’t really work with one word answers
edit: I just double checked and open doesn’t return anything on stdout if you only put the path to the container, if you put the path to the executable as above, you should see its stdout, let me know if you try that and if it returns anything interesting?
If this is not resolved, you may want to remove the “solved” mark.
1 Like