Victor Choi

  • Home
  • Business
    • Internet
    • Market
    • Stock
  • Parent Category
    • Child Category 1
      • Sub Child Category 1
      • Sub Child Category 2
      • Sub Child Category 3
    • Child Category 2
    • Child Category 3
    • Child Category 4
  • Featured
  • Health
    • Childcare
    • Doctors
  • Home
  • Business
    • Internet
    • Market
    • Stock
  • Downloads
    • Dvd
    • Games
    • Software
      • Office
  • Parent Category
    • Child Category 1
      • Sub Child Category 1
      • Sub Child Category 2
      • Sub Child Category 3
    • Child Category 2
    • Child Category 3
    • Child Category 4
  • Featured
  • Health
    • Childcare
    • Doctors
  • Uncategorized

7/19/2019

How to handle a iOS extension using fastlane

 6:17 PM     app profile, cicd, fastlane, fastlane gym, fastlane match, fastlane produce, iOS Development, notification extension, onesignal, provisioning profile     No comments   

An app that I developed uses OneSignal to send a push notification. OneSignal’s way that they provide a push notification service is using a notification extension in iOS. In this case we have a situation on iOS CI/CD process. Before you dive into handling this issue you should know that each extension in iOS has a different provisioning profile. So we need to create an app profile in Apple developer portal.

Create an app profile for your extension

You can use fastlane produce function to create an app profile for your extension. If you already have an app profile in Apple Developer portal, pass this instruction.
lane :createAppProfile do
produce(
    app_identifier: “com.victorchoi.x.OneSignalNotificationServiceExtension",
    app_name: “victorchoi OneSignalNotificationServiceExtension",
    skip_itc: true
)

Create a provisioning profile

Then you need to create a certificate and a provisioning profile for your extension. I use fastlane match to easily create and manage a certifcate and a provisioning profile.
lane :codesign do 
 match(
      app_identifier: ["com.victorchoi.x”,”com.victorchoi.x.OneSignalNotificationServiceExtension"],
      type: "appstore",
)

Download the provisioning profile and save into your CI/CD server

Lastly, you need to make sure that your CI/CD server has the provisioning profile to build. At this step, you must have two provisioning profile for your app. So let’s configure your provisioning profile in the build process. In this case, I use fastlane gym to build them.
provisioningProfiles: { 
   “com.victorchoi.ios” => "match AppStore com.victorchoi.ios“,
   “com.victorchoi.x.OneSignalNotificationServiceExtension" => "match AppStore com.victorchoi.x.OneSignalNotificationServiceExtension"
}

Building your CI/CD process takes time. So I hope this article helps you not to spend much time on it.
Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Google+
  •  Stumble
  •  Digg

No Profile for team error on Jenkins using fastlane gym

 5:03 PM     devops, fastlane, gym, iOS Development, jenkins, no profile for team, xcode     No comments   

I prefer to use a combination of Jenkins and fastlane to build and distribute my iOS application. Recently I tried to make a CI/CD server using Jenkins and fastlane and then I faced an issue that I had struggled to fix it. The issue is normally coming from a build process using gym in fastlane. The error log is normally like below.

No profile for team 'TXVIGNOXXXX’ matching ‘iPhone_Development' found: Xcode couldn't find any provisioning profiles matching 'TXVIGNOXXXX/iPhone_Development'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the General tab of the target editor 

So how do I solve this issue?

  1. Check your Provisioning Profile Mostly you can find this advice on the web. Provisioning Profile files are saved in the path /Users/{{UserAccount}}/Library/MobileDevice/Provisoning Profiles and then your right provisioning file should be there. But my case wasn’t like this. I use fastlane match to create and update Provisioning Profile and there should not be this issue.

  2. Check your Team ID Find your team ID and then check the Team ID is correct.

  3. Permission issue The third one was my issue. In my case, I use sudo command to run fastlane release. But the problem was the Provisioning Profile belongs to Jenkins user account. Then I just removed the sudo command and then now it works. Still, I am not 100% sure that the issue was caused by the permission to run fastlane command.

I hope that this article could help someone has a similar issue.

Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Google+
  •  Stumble
  •  Digg
Newer Posts Older Posts Home

Search This Blog

Popular Posts

  • How to put a padding into a UITextField ?
  • Keynote Tutorial Text Outline - Make your animation meaningful
  • Keynote Tutorial , Sound is a design,too
  • Keynote Tutorial How to improve your bullets

Blog Archive

  • ►  2020 (2)
    • ►  January (2)
  • ▼  2019 (21)
    • ►  December (2)
    • ►  November (6)
    • ►  October (5)
    • ►  September (2)
    • ►  August (3)
    • ▼  July (2)
      • How to handle a iOS extension using fastlane
      • No Profile for team error on Jenkins using fastlan...
    • ►  June (1)
  • ►  2017 (11)
    • ►  December (2)
    • ►  November (2)
    • ►  July (2)
    • ►  May (1)
    • ►  April (1)
    • ►  March (3)
  • ►  2016 (48)
    • ►  December (3)
    • ►  November (2)
    • ►  September (1)
    • ►  August (10)
    • ►  July (5)
    • ►  June (7)
    • ►  May (2)
    • ►  April (18)
Powered by Blogger.

Navigation Menu

  • Home
  • About
  • Documentation
  • Contact

Contact Us

Name

Email *

Message *

Copyright © Victor Choi | Powered by Blogger
Design by Hardeep Asrani | Blogger Theme by NewBloggerThemes.com | Distributed By Gooyaabi Templates