MultiBranding相同的源代码而不使用xcode

Question

我有一个应用程序,我想将它标记为3个不同的应用程序与不同的用户界面.

我不想直接使用Xcode.

到目前为止,我发现了很多解决方案,它们可以创建不同的目标并拖放图像

但我打算在Xcode之外做这个品牌推广工作



帮帮我 !

Answer 1

现在我们可以在不打开 Xcode 的情况下构建代码

品牌 （UI、构建设置和功能）

• 用户界面
  • 应用程序图标和其他图标
  • iTunes 艺术作品
• 构建设置
  • 应用程序名称
  • 捆绑包标识符
  • 配置文件
  • 代码签名身份
• 功能性
  • 品牌特定 URL（登录、注销、资源获取等...）

使用终端

品牌.sh

   #Author: Durai Amuthan(h.duraiamuthan@gmail.com)
#This is to achieve multiple branding of an iOS app by configuring the variables below

#************ Configuring the brand starts ************

#Directory path where .xcworkspace or .xcodeproj exists
PathOfProjectDirectory=/Users/Shared/Jenkins/Documents/JenkinsTestNuu/New/

#Path where info.plist exists
PathOfInfoPlist=$PathOfProjectDirectory/XxYyZz

#Path to icons where new iTunesArtwork and application icon exixts
#Note: Make sure proper naming conventions of file has been followed
PathOfNewIcons=/Users/Shared/Jenkins/Documents/icons-two

#Path to asset resource where you have kept your application icon.
PathOfAppIconSet=$PathOfProjectDirectory/XxYyZz/Icon.xcassets/AppIcon.appiconset

#Path where do you want the .app file has to be kept
PathToApp=/Users/Shared/Jenkins/Documents/JenkinsTestNuu/app

#Path where do you want the .ipa file has to kept
PathToIpa=/Users/Shared/Jenkins/Documents/JenkinsTestNuu/ipa

#Cocoapods project or project that involves more than one modules are scheme based
isWorkspaceBased=true

#Path of the Project (.xcodeproj) - applicable for workspace(.xcworkspace) based project
PathofProjectFile=$PathOfProjectDirectory/XxYyZz.xcodeproj

#Path of the Workspace (.xcworkspace)
PathofWorkspaceFile=$PathOfProjectDirectory/XxYyZz.xcworkspace

#Name of the target - applicable only for non-workspace(.xcodeproj)  based projects
Target=XxYyZz

#Scheme of the iOS app
Scheme=XxYyZz

#To ascertain Cocoapods has been used or not
isCocoaPodsBased=true

#Configuration of the app (Debug -(Development) or Release(Adhoc or Distribution))
Config=Release

#For giving access to signing idetity found in KeyChain
LoginKeychainPath=/Users/Shared/Jenkins/Library/Keychains/login.keychain
LoginKeyChainPassword=xxyyzz

#Name of the code signing identity.You can find the name in Keychain or xcode build setting
CodeSigningIdentity='iPhone Distribution: Xx Yy Zz Limited (3Z5MHUYJ2L)'

#Path of the provisioning profile
PathToMobileProvision=/Users/Shared/Jenkins/Desktop/BrandingTest.mobileprovision

#UUID value found inside Provisioning profile has to be given
#Do not forget to install provisiong profile in the system
ProvisioningProfileIdentity=6e6506e9-8233-4886-9084-zf21e8f8bbae

#Bundle identifier of the app
BundleIdentifier=com.xxyy.zz

#AppVersion of the app
AppVersion=2.2.2

#App Name
Appname=Two

#************ Configuring the brand ends ************

#** Creatting the build based on configuration starts **

cd $PathOfInfoPlist
echo "****************** Setting App Name ******************"
/usr/libexec/PlistBuddy -c "Set :CFBundleName $Appname" info.plist
/usr/libexec/PlistBuddy -c "Set :CFBundleDisplayName $Appname" info.plist
echo "app name has been set as $Appname"

cd $PathOfProjectDirectory
echo "****************** Setting AppVersion ******************"
/usr/bin/agvtool new-marketing-AppVersion $AppVersion
/usr/bin/agvtool new-AppVersion -all $AppVersion

echo "****************** Changing app icons & iTunes Artwork ******************"
cp -R $PathOfNewIcons/*.png $PathOfAppIconSet
echo "App icons has been changed at $PathOfNewIcons"
cp -R $PathOfNewIcons/iTunesArtwork@2x $PathOfProjectDirectory/XxYyZz
cp -R $PathOfNewIcons/iTunesArtwork $PathOfProjectDirectory/XxYyZz
echo "iTunesArtwork has been changed at $PathOfProjectDirectory"

#Unlock login keychain
security unlock-keychain -p $LoginKeyChainPassword $LoginKeychainPath
if $isCocoaPodsBased == 'true'
then
echo "****************** Installing Cocoapods **********************"
/usr/local/bin/pod install
echo "Cocoapods has been installed"
fi

echo "****************** Creating .app ******************"
if $isWorkspaceBased == 'true'
then
/usr/bin/xcodebuild -scheme $Scheme -workspace $PathofWorkspaceFile -configuration $Config clean build CONFIGURATION_BUILD_DIR=$PathToApp "CODE_SIGN_IDENTITY=$CodeSigningIdentity" "PRODUCT_BUNDLE_IDENTIFIER=$BundleIdentifier" "PROVISIONING_PROFILE=$ProvisioningProfileIdentity"
else
/usr/bin/xcodebuild -target $Target -project $PathofProjectFile -configuration $Config clean build CONFIGURATION_BUILD_DIR=$PathToApp "CODE_SIGN_IDENTITY=$CodeSigningIdentity" "PRODUCT_BUNDLE_IDENTIFIER=$BundleIdentifier" "PROVISIONING_PROFILE=$ProvisioningProfileIdentity"
fi
echo ".app has been generated at $PathToApp"

echo "****************** Creating .ipa *******************"
/usr/bin/xcrun -sdk iphoneos PackageApplication -v $PathToApp/XxYyZz.app -o $PathToIpa/$Appname.ipa --embed $PathToMobileProvision --sign "$CodeSigningIdentity"
echo "$Appname.ipa has been generated at $PathToIpa"

#** Creatting the build based on configuration ends **

该文件具有自我描述性，您可以轻松理解。只需在文件中配置变量的值并按如下所示调用它

sh Branding.sh

供参考：

如果您想要除了应用程序图标和 iTunesArtwork 之外的其他一些图标也可以更改，请使用cp命令，例如

cp path/to/source path/to/destination

要了解更多信息，请执行以下操作：cp man

使用上面的文件，您可以为 UI 和构建设置进行品牌化。

对于功能性品牌，你必须保留

• 品牌特定 URL

• 与品牌相关的其他投入

在一个单独的 plist 文件中，以便在构建应用程序时也可以根据各自的品牌更改这些内容

在编码方面，您可以自定义应用程序以从 plist 中读取值，如下所示

函数定义：

func getPlistFile()->Dictionary<String,AnyObject>? {
        var dictPlistFile:Dictionary<String,AnyObject>?
        if let path = NSBundle.mainBundle().pathForResource("plistfile", ofType: "plist") {
            if let dictValue = NSDictionary(contentsOfFile: path) as? Dictionary<String, AnyObject> {
                dictPlistFile=dictValue
            }
        }
        return dictPlistFile
    }

函数调用：

var Value=getPlistFile()?["Key"]

您可以在构建应用程序时使用PlistBuddy根据品牌更改键的值

这是语法

/usr/libexec/PlistBuddy -c "Set :Key Value" plistfile.plist

使用詹金斯

我们可以在 jenkins 中有效地重用 shell 脚本

1.您必须使用“添加参数”对 jenkins 中 shell 脚本中的所有变量进行参数化...就像下面的屏幕截图一样，我已经对一个变量进行了操作，就像您必须对所有其他变量进行操作一样

2.在构建步骤中选择执行shell

3.复制创建基于配置的构建开始和创建基于配置的构建结束之间的脚本并将其粘贴到执行Shell中

笔记：

• 资源规则

  在通过非 xcode 接口构建和打包应用程序时，某些版本中存在关于Xcode ResourceRules的已知错误。

  因此，必须运行一次才能在Xcode中停用对资源规则路径的验证。资源规则路径已弃用，并且苹果不接受带有资源规则的应用程序，但如果我们在不使用 Xcode 的情况下构建应用程序，则会出现验证错误：未找到资源规则会出现反驳，表明我们只需运行脚本一次。

xcode_fix_PackageApplicationResourceRules.sh

#!/bin/sh
# A script to patch xcrun PackageInstallation so that it doesn't use the deprecated --resource-rules
# See "Do not use the --resource-rules flag or ResourceRules.plist. They have been obsoleted and will be rejected."
#   under https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG205
# Reported as Apple bug #19384243
# 
# should be run as a user who can modify the PackageApplication file

xcodedir=$1

function usage {
        # FIXME we cannot parse args properly because 2 are optional...
        echo "USAGE: $0 xcodedir"
        echo "  xcodedir: an install dir like /Application/Xcode6.1.1.app"
}

if [[ $# -ne 1 ]]; then
        echo "ERROR: invalid number of arguments"
        usage
        exit -1 
fi

pi="$xcodedir/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/PackageApplication"
piorig="$piOrig"

if [[ ! -f "$pi" ]]; then
    echo "$pi file not found. Invalid argument ?"
    usage
    exit -1
fi

grep resource-rules "$pi" 
if [[ $? -ne 0 ]]; then
    echo "PackageApplication doesn't use resource-rules. Skipping"
    exit 0
fi

if [[ -f "$piorig" ]]; then
    echo "Backup file $piorig already exist. Aborting"
    exit -1
fi

perl  -p -i'Orig' -e 'BEGIN{undef $/;} s/,resource-rules(.*sign}).*ResourceRules.plist"/$1/smg' "$pi" 
echo $?

• 解锁钥匙扣

  每当您在终端中运行 Branding.sh 时，它都会提示用户名和密码作为其访问系统钥匙串

  每当您在 jenkins 中运行作业时，您都会收到“不允许用户交互”错误

  所以要解决这个问题，您必须按照以下步骤操作

  • 打开钥匙串访问
  • 右键单击私钥
  • 选择“获取信息”
  • 选择“访问控制”选项卡
  • 单击“允许所有应用程序访问此项目”
  • 点击“保存更改”
  • 输入您的密码

• 配置文件

  如果您收到“未找到匹配的配置文件”，请确保您已双击并通过 Xcode 安装它。

  安装后，您将在~/Library/MobileDevice/Provisioning Profiles/中看到UUID.mobileprovision

  此 UUID 是移动配置内的值，表示已安装配置文件。

我希望这可以帮助你