Installation Troubleshooting

Archiving Fail Error on Fat-framework

Add script on Target's Build Phase - New Run Script Phase

#!/bin/sh

echo "\n ⏱ Removing Unused Architectures \n\n\n"

exec > /tmp/${PROJECT_NAME}_archive.log 2>&1

FRAMEWORK="ChannelIO"

FRAMEWORK_EXECUTABLE_PATH="${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}/$FRAMEWORK.framework/$FRAMEWORK"

EXTRACTED_ARCHS=()

for ARCH in $ARCHS

do

lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"

EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")

done

lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"

rm "${EXTRACTED_ARCHS[@]}"
rm "$FRAMEWORK_EXECUTABLE_PATH"
mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"

echo "\n ⏱ Removing Unused Architectures \n\n\n"
echo "\n\n\n 🏁 Completed removing unused architectures from your fat framework."
echo "\n\n\n 🔍 For more details please check the /tmp/${PROJECT_NAME}_archive.log file. \n\n\n"

LLDB: Couldn't IRGen Expression Debug Error

There is some swift debug bug on xcframework with Cocoapod and Xcode. We are working to resolve this issue quickly.
There is temporary solution

When an error such as 'ITMS-90680' or 'ITMS-90685' occurs in the environment using SPM and Extension

In an environment where SPM and Extension are used, errors such as'ITMS-90680' or'ITMS-90685' may occur during the App Store upload process.
This is an SPM error. When using an extension in an environment using a binary framework through SPM, the binary package is copied equally to the Plugins folder.

It can be solved by adding a script to Build Phases:

# https://forums.swift.org/t/swift-package-binary-framework-issue/41922
#!/bin/bash

COUNTER=0
while [ $COUNTER -lt "${SCRIPT_INPUT_FILE_COUNT}" ]; do
    tmp="SCRIPT_INPUT_FILE_$COUNTER"
    FILE=${!tmp}

    echo "Removing $FILE"
    rm -rf "$FILE"
    let COUNTER=COUNTER+1
done

In iOS 14 or later, the link or link button is not clicked

In iOS 14 or later, link navigation may not work if you change the default browser settings.
This is an iOS bug, which can be fixed by adding the below to info.plist.

<plist>
<dict>
  ...
  <key>LSApplicationQueriesSchemes</key>
  <array>
    <string>http</string>
    <string>https</string>
  </array>
  ...
</dict>
</plist>