You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@DjArt Hello,
First of all, many thanks for your Windows.Internal.Calls project - this is really a great job!
I am now trying to use it in Windows 10 running on ARM. A thing that I have noticed, is that there is no proper way for the app to react on incoming call - CallOriginDataRequest PhoneTrigger or CommunicationBlockingAppSetAsActiveTrigger are not working, and portions of UWP extensions for Mobile, like PhoneCallOriginManager.ShowPhoneCallOriginSettingsUI or CommunicationBlockingAppManager.ShowCommunicationBlockingSettingsUI do not seem to work for Universal. However, in your Windows.Internal.Calls project I have noticed some endpoints of interest in PhoneOm exports, like IsCallOriginManagerSupported or PhoneGetActiveAppByType. These imports look like stubs at the moment. Provided that the standard Phone app on Windows 10 reacts on incoming calls, I hope there is a possibility that PhoneOm has proper functions to support this functionality and properly declare an app as a valid call origin provider or communications filter.
I wonder if creating a separate issue would be a more proper place for this discussion?
No description provided.
The text was updated successfully, but these errors were encountered: