Custom framework naming conflicts with Apple's private frameworks

Question

Created Mar ’23

Replies 1

Boosts 0

Participants 2

Linking a custom dynamic iOS framework named FMCoreLite was crashing the app during runtime. And the crash log has a weird information about some classes inside FindMyDevice framework.

dyld[90390]: Symbol not found: _OBJC_CLASS_$_FMPreferencesUtil
  Referenced from: &lt;6FCA1A20-3728-39C5-BBB8-9BF918E6DC0C> &#x2F;Applications&#x2F;Xcode.app&#x2F;Contents&#x2F;Developer&#x2F;Platforms&#x2F;iPhoneOS.platform&#x2F;Library&#x2F;Developer&#x2F;CoreSimulator&#x2F;Profiles&#x2F;Runtimes&#x2F;iOS.simruntime&#x2F;Contents&#x2F;Resources&#x2F;RuntimeRoot&#x2F;System&#x2F;Library&#x2F;PrivateFrameworks&#x2F;FindMyDevice.framework&#x2F;FindMyDevice
  Expected in:     &lt;B153C426-DA0D-3E58-A586-087B00CB9FE6> &lt;path-to-deriveddata>&#x2F;Build&#x2F;Products&#x2F;Debug-iphonesimulator&#x2F;FMCoreLite.framework&#x2F;FMCoreLite

It seems like Apple also has a private framework named FMCoreLite (https://iphonedev.wiki/index.php/PrivateFrameworks) and that is creating some conflicts. Renaming custom framework with a slight change (FMCore_Lite) in its name fixes the issue.

Is this expected to avoid naming conflicts with the private frameworks ? Is there a documentation/article available about this information ?

Boost

Answer 1

AndyJJ OP

Mar ’23

Don't have a link for you, but remember vaguely reading that all two caps prefixed framework names are reserved for Apple and others should use names prefixed with three or more caps letters. So a name for a non-Apple framework should be something like FMXCoreLite or something. Forgive me if this is rubbish, cannot check at this time.

0