Conversation
Enables Bear.app to recognize that it is expected to provide response to its action
These changes do not address issue of Bear not calling back to xcall. Thanks to u/trix180 for helping me understand that :)
Fix for issue martinfinke#4. Reason is that MacOS was not always able to identify particular xcall.app instance as 'xcall066958CA' protocol owner which caused sometimes inability to get x-success/x-error responses Project preferences changes in URL Types section: - Role changed from 'Viewer' to 'Editor' to allow xcall.app to be identified by MacOS as protocol owner - Added identifier of original xcall.app developer - Martin Finke
|
Finally I was able to fix the problem for me and I believe for others who experienced it too. Reason was that MacOS was not always able to identify particular xcall.app instance as an owner of 'xcall066958CA' protocol which caused sometimes inability to get x-success/x-error responses - they were just routed somewhere else by OS. Changing app's role from URL Scheme 'viewer' to URL Scheme 'Editor' made it work for me consistently. Project preferences changes in URL Types section:
|
pr1mal
changed the title
|
I am having the same issue with Bear.app and would like to use your PR'd Version. |
|
nevermind @pr1mal - I managed to build it myself. Your fix works well, thanks a lot! |
|
I would just like to add that this fix works for me as well. My focus is using bear to return tags and this code works perfectly - thanks! |
3 participants
This is potential fix for No return value #4.
With this fix in place, I'm able to make Bear.app to respond using x-success.
Changes that actually address the issue are in AppDelegate.m, the rest changes I made to be able to build project with latest XCode, so they might be unnecessary.