#xcode8

[youngsterdev-blog]

Like & Share

[giniland-blog]

[Swift3＆Xcode8]タブ切り替える度にwebviewリロードするswift3コード

ViewLoad,ViewAppear処理について viewDidLoad ・View が初めて呼び出される時に1回だけ呼ばれます。 ・アプリ起動後に初めて当Viewが表示された場合に1度だけ呼ばれます。 viewWillAppear ・View が表示される直前に呼ばれるメソッド ・タブ等の切り替え等により、画面に表示されるたびに呼び出されます。 ・タブが切り替わるたびに何度でも呼ばれます。 viewDidAppear ・View の表示が完了後に呼び出されるメッソド ・タブ等の切り替え等により、画面に表示されるたびに呼び出されます。 ・タブが切り替わるたびに何度でも呼ばれます。 viewWillDisappear ・View が他のView (画面から消える) 直前に呼び出されるメッソド ・View が他のView (画面から消える) 直前に呼び出されるメッソド…

View On WordPress

[perfectforwarding]

C enum types in llvm 8.0

I have some old third-party (1990s) C code in one of my iOS projects.  Occasionally updating to a new version of Xcode breaks the build with a lot of the dodgier elements left in this code.  Updating to Xcode 8.1 resulted in some multiply defined symbols in code that previously linked without trouble.

SomeHeader.h

enum { ST_LOCKINT = (1 << 0), ST_DD = (1 << 1), /* ix */ ST_FD = (1 << 2), /* iy */ ST_CB = (1 << 3) /* DDCB FDCB (ii+d) write back */ } KMZ80_STATE;

vs.

enum KMZ80_STATE { ST_LOCKINT = (1 << 0), ST_DD = (1 << 1), /* ix */ ST_FD = (1 << 2), /* iy */ ST_CB = (1 << 3) /* DDCB FDCB (ii+d) write back */ };

Functionally for the client code these two implementations are identical.  However the first means of defining the enum actually defines an unnamed enum and an instance of it _KMZ80_STATE.  This is a no go if multiple C files include this header.

[danielalbu]

Error ITMS-90167: “No .app bundles found in the package”

After upgrading my MacBook Pro to the latest macOS, Sierra, I’ve noticed that I can no longer upload distribution builds from XCode 7.3.1 to the Appstore.

Everytime it started uploading the build to the Appstore, I would get the following error:

(Error ITMS-90167: “No .app bundles found in the package”)

I’ve tried a few workarounds to no avail and it seems that the only way (at the moment) to upload XCode 7.3.1 builds is to follow these steps:

1. Archive the build (Product -> Archive)

2. Once the archive is ready, right click it in the Organizer window and choose Show In Finder

3. Right click the .xcarchive file and click Show Package Contents

4. Once within the .xcarchive file, go to the Products folder, then Applications folder and finally select the XX.app file (XX is your app name), right click it and choose Show Package Contents.

5. Once inside that package, go to the Info.list file and open it.

6. Edit the value BuildMachineOSBuild and change its value to 15G31 (which is the latest El Capitan version) 

That’s it! Now you can upload the build using XCode 7.3.1.

If you are still running into the same problem after all this, you can try using this final step:

7. Install XCode 8 (Make sure you don’t overwrite XCode 7.3.1 - in case you still need it for Swift 2.2 or lower projects) and upload the build using XCode 8′s Application Loader.

This should do the trick.

[mobileways]

Apple Developers: What's new in Xcode 8, Swift 3 and iOS 10.

Having waited for these updates for a while, we are as much excited as you are - a new version of Xcode is now out alongside Swift. Xcode 8 is bundled with SDKs for iOS 10, watchOS 3, tvOS 10, and macOS Sierra.                                                       To work with Xcode 8 make sure you have macOS Sierra 10.12 or OS X El Capitan 10.11.5 or later.

The major consideration for you in this update is, Xcode 8 came up with new version of swift language, which also has Swift 3 migration process specified while opening your existing projects(built using Swift 2 or previous versions of Swift). There is no need for you to worry, because Xcode has migrators that help you in the due process and we suggest you to look at the every code change that the migrator is trying to do as that's one way to identify some of the syntactic differences in Swift 3. Xcode 8 also supports Swift 2.3, however If your code is in Swift 2.2, you need to make it to Swift 2.3 using Swift migrator in order to work with Xcode 8. And be ready, as Apple said, Swift 2.3 will also be removed in future update of Xcode, hence ensure you shift to Swift 3 as soon as possible.

1. Xcode 8

We have learned few highlights of Xcode 8 from Apple:

Security: The security in the 'Xcode.app' has been increased. It will provide the more secured development environment eventually avoiding Malware in iOS.

Readability: The code editor also was improved for the best readability.

Downloading: This time Xcode has smaller download size and faster installation for App Store downloads. If you want to download Xcode as a distributable package other than from App Store, you should check "https://developer.apple.com/download/more/"(Login is required). This time Xcode file has an extension .xip(extract in place) rather than regular (.dmg). Xip file is similar to a zip file but it has digital signatures in addition, it is to ensure more security. When you download 'Xcode.xip' file and open, you'll see the app extracted in the same downloads folder. You should now move it to the application folder if you want to do so. But we suggest you to keep the previous version of Xcode also as it is flexible for some of your existing projects until you completely migrate them to Swift 3.

Accessibility: It's been said that accessibility is also enhanced in core Interface Builder workflows, and throughout the Xcode in this update.

Usability: Xcode and Interface Builder improvements are made to increase the performance and to make them work faster.

Reference: Includes Documentation improvements.

Modules:

Certificates Signing

'Capabilities' module in Xcode targets

Asset Catalogs

Source editing

Debugging

Instruments

Testing modules

Source control

Xcode server

Sometimes, we face some crashes with Xcode while working in projects. Users feel irritated when any app crashes while using the app, as developers we feel the same when IDE crashes. But we have to understand that unfortunately every software has its own bugs. So, we have a great hope ahead in Xcode 8 interms of its stability and look forward to work with it. Download Xcode 8 from App Store and try it on.

2. Swift 3:

As you aware, Swift is open source, and it has a great community of developers, So we always tend to get the best in every latest version of Swift programming language. Check Apple's ' The Swift Programming Language (Swift 3) ' To explore more on Swift 3.

Important frameworks such as 'Core Graphics' and 'Grand Central Dispatch' have been upgraded to native swift interfaces in Swift 3. Its good to know that improvements in API naming to enhance the code's consistency and clarity are done. Swift 3 also has many new features added. To know more about the language changes check Apple's Swift 3 language changes. The best way to experiment with Swift 3 is by using Apple's Swift Playgrounds app for iPad.

3. iOS 10:

Not long ago we have updated our devices to iOS10. It seems, that updating iOS software in our devices is a two step process now. When we initiate the iOS update in our devices from the version iOS 9.3.3(or lower), first we get updated to the version of iOS 9.3.5, then we need to again initiate the update explicitly to get the version iOS 10.0.1. We are not very sure if the same flow happens with your devices, but this is what happened to us.

To elaborate more, iOS 10 SDK has come up with new APIs and services. And the major thing we have observed is, your apps can now communicate with some of the default iOS apps to do certain functionalities as per the requirement.

For example your apps can engage with the following default iOS apps or services such as:

Messages

Siri

Phone

Maps

Lets now try to understand the interactions with some of the apps mentioned above :

Interaction with Messages app:

Using the new Messages framework introduced in iOS 10, you can create an app extension which helps the users to interact with your app directly within messages app.

Two things can be done here.

1. Stickers:

    By simply placing your images in Xcode, you can create packages of stickers which can be used by the users directly in iMessage app. However no code is required to create such a Sticker pack.

2. iMessage Apps:

   You can create an app extension which can be seen in iMessage app, which enables the users to gain access to your apps directly from iMessage app without leaving the conversation.

Interaction with Siri:

        We now have the privilege to work with Siri in iOS10. Users can interact with your app using voice command and access certain services like ride booking and personal payments. Siri Kit will help you to achieve this. We are truly exited to step into this implementation.

Following are the supported domains by SiriKit:

Audio or video calling

Messaging

Sending or receiving payments

Searching photos

Booking a ride

Managing workouts

Adjusting settings in a CarPlay-enabled vehicle (automotive vendors only)

Making restaurant reservations (requires additional support from Apple)

Interaction with Phone app:

If your app is VoIP related, you can interact with iOS default phone app. Calls can be directly displayed on the lock screen. You need to use CallKit framework to make this implementation.

Interaction with Maps app:

If your app has the implementation related to maps, you can create an extension with your custom content which can be injected into iOS default Maps app, enabling users to directly communicate with your app from Maps app. 'IntentsUI.framework' will help you do that.

Let's now look at some more services that we can make use of, in iOS 10.

User Notifications:

We have really enjoyed this framework in iOS 10, as it redefines the way notifications look and behave in iOS devices. Following are the two new frameworks that you can effectively make use of:

UserNotifications.framework

UserNotificationsUI.framework

Using UserNotifications.framework you can handle local and remote notifications. This framework is used to schedule the delivery of notifications based on specific conditions, such as time or location.

UserNotificationsUI.framework will you give you the privilege to customize the appearance of local and remote notifications when they appear on the user's device. You can use this framework to create an app extension which can receive the notification data and provides the corresponding visual representation. Your extension can also respond to custom actions associated with those notifications.

Speech Recognition:

iOS 10 has new API that can recognize speech and convert it into text. It can be used in both real-time and recorded audio. You need to use Speech.framework for this. User permission is required to perform speech recognition. To request the user’s permission, you must add the NSSpeechRecognitionUsageDescription key to your app’s Info.plist file and provide content describing your app’s usage.

App Search Enhancements:

Using Core Spotlight framework in iOS 10 you can do several enhancements to app search:

In-app searching

Search continuation

Crowdsourcing deep link popularity with differential privacy

Visualization of validation results

Widget Enhancements:

You can observe few UI changes on lock screen of iOS 10, meaning widgets can be displayed on top the lock screen which was only accessible in the notification drawer. However now you can directly swipe right so see widgets. To ensure that your widget looks good on any background, you can specify  widgetPrimaryVibrancyEffect or widgetSecondaryVibrancyEffect. Displaying mode can be specified using NCWidgetDisplayMode allowing the user to choose either compact or expanded view.                                                  

In addition to the above services, iOS 10 included many other features, along with some additional framework changes. Please refer Apple's iOS 10 Document for more details.

Stay tuned to know more about iOS updates.

[script-ease]

update_xcode_plugins - No more messing with plugin UUIDs; Plugins on Xcode 8!

[dlosuna]

Code Signing in Xcode 8 - Possible Mobile

Xcode 8 provides a solution to our code signing and provisioning profile grievances.