public interface CallBridge

Internal service-provider interface implemented by each platform port to carry the com.codename1.call API onto the native call stacks: Apple’s CallKit and PushKit, and Android’s ConnectionService, TelecomManager and CallScreeningService.

Application code never touches this interface. It is obtained by the com.codename1.call packages from com.codename1.ui.Display#getCallBridge(), and the base implementation returns null – which is why the public API degrades to a well-behaved NOT_SUPPORTED on ports that implement nothing, and why application code needs no platform if statements.

Everything here is primitives, strings and byte arrays

A port may be Objective-C reached through ParparVM, where constructing a Java object is expensive and easy to get wrong. So no method on this interface takes or returns a framework type: enums cross as their ordinals, capability sets cross as bit masks, and structured records cross as tab-delimited strings built by com.codename1.impl.call.CallWire.

Asynchrony is by request id, and every operation must answer

Operations that can fail take a requestId allocated by the caller and answer exactly once by calling the matching deliver... entry point on the public class. An operation that never answers is worse than one that fails: the caller holds an AsyncResource that will never settle and has no way to find out. A port that cannot start something must still report the failure. This bites harder here than elsewhere, because both platforms have a documented “the system refused your call” path – Telecom’s onCreateIncomingConnectionFailed and the NSError handed to CallKit’s report completion – that is easy to leave unwired, and an unwired refusal looks exactly like a call that is still ringing.

Unsolicited events – the user answering, the system taking the audio – carry the call id they belong to instead of a request id. Every entry point may be called from any thread; they marshal to the EDT themselves.

The up direction has a deadline too

A system-originated action must be answered with completeAction within a few seconds or the platform times it out and the system UI and the app disagree about the call, silently. The facade guarantees an answer the same way this interface guarantees one downward.