Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid iMessage App, as in #23 #29

Closed
evgeny-detkov opened this issue Mar 15, 2018 · 2 comments
Closed

Invalid iMessage App, as in #23 #29

evgeny-detkov opened this issue Mar 15, 2018 · 2 comments

Comments

@evgeny-detkov
Copy link

Hello! I have a similar situation: "Invalid iMessage App - Your iMessage app contains an invalid sticker pack. .... "
I use Unity 5.6.1f1, xcode 9.2.
The build is automated through teamcity.
The screenshots from issue #23 fit my case one on one.
bundleId my application in a format, for example, com.company.app
bundleId project with stickers - com.company.app.stickers
In developer.apple.com two provisioned profiles were created and two AppsID for bundleId .
Sticker files are named as sticker_01.png, sticker_02.png, etc.
IMessage App icons are all correctly installed.
The Unity project for the test is empty, only the stickers and your iMessageStickerUnity-plugin have been added.
What else can you do and check? Help me, please.

@evgeny-detkov
Copy link
Author

Another fact: for the main bundleId in the provision-profile push-notifications are enabled. In the provision-profile of the stickers push-notifications is disabled...

@evgeny-detkov
Copy link
Author

evgeny-detkov commented Mar 18, 2018

I found a solution!
The build project was not accepted by Apple due to the lack of files created when the project was archived.
The article was helped by https://blog.bitrise.io/new-export-options-plist-in-xcode-9
I created the file exportOptionsPlist.plist
Then I used it on the command line in teamcity:

1 step (build xcode):

  cd %teamcity.build.workingDir%/ios/
  xcodebuild -project Unity-iPhone.xcodeproj \
  -scheme Unity-iPhone \
  CODE_SIGN_IDENTITY=<name_your_distribution_certificate>" \
  -archivePath build/myApp.xcarchive archive

2 step (create ipa):

  cd %teamcity.build.workingDir%/ios/
  xcodebuild -exportArchive -exportOptionsPlist exportOptionsPlist.plist -archivePath 
  build/myApp.xcarchive -exportPath build/export
  mv build/export/Unity-iPhone.ipa build/myApp.ipa

3 step (upload ipa):

  "/Applications/Xcode.app/Contents/Applications/Application 
  Loader.app/Contents/Frameworks/ITunesSoftwareService.framework/Versions/A/Support/altool" --
  upload-app -f "ios/build/myApp.ipa" -u %itunes_user_login% -p %itunes_user_password%

As a result, the file exportOptionsPlist.plit looked like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>method</key>
	<string>app-store</string>
	<key>provisioningProfiles</key>
	<dict>
		<key>com.company.app1</key>
		<string><name profision profile app1 (main app)></string>
		<key>com.company.app2</key>
		<string><name profision profile app2 (stickers app)></string>
	</dict>
	<key>signingCertificate</key>
	<string>iPhone Distribution</string>
	<key>signingStyle</key>
	<string>manual</string>
	<key>stripSwiftSymbols</key>
	<true/>
	<key>teamID</key>
	<string><your team id></string>
	<key>uploadBitcode</key>
	<false/>
	<key>uploadSymbols</key>
	<false/>
</dict>
</plist>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant