$ bundle exec pod install Re-creating CocoaPods due to major version update. Analyzing dependencies [!] The dependency `AFNetworking (= x.x.x)` is not used in any concrete target. The dependency `Xxxxxxxxxx (= x.x)` is not used in any concrete target. . . . .
エラーの意味通り、使ってないよー。
Podfile には案の定 xcodeproj でプロジェクト名を記載していた。
platform :ios, '10.0' project 'Xxxxxxx.xcodeproj' pod 'AFNetworking', 'x.x.x' pod 'Xxxxxxx', 'x.x'
以下のように変更。
platform :ios, '10.0' project 'Xxxxxxx.xcodeproj' target 'Xxxxxx' do pod 'AFNetworking', 'x.x.x' pod 'Xxxxxxx', 'x.x' end
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
$ bundle exec pod install Re-creating CocoaPods due to major version update. Analyzing dependencies [!] The dependency `AFNetworking (= x.x.x)` is not used in any concrete target. The dependency `Xxxxxxxxxx (= x.x)` is not used in any concrete target. . . . . [!] `xcodeproj` was renamed to `project`. Please update your Podfile accordingly.
Android: 'android' is deprecated; use 'com.android.application' instead
Android Studio 上で build.gradle の整理をしているときに気付いたのですが、apply plugin: 'android' に打ち消し線が入るようになっていました。
こんなのです↓
'android' is deprecated; use 'com.android.application' instread This detector looks for deprecated Gradle constructs which currently work but will likely stop working in a future update.
Android Studio のバージョンいくつから付くようになったのかは分かりませんが、非推奨と言われてしまったら変えざるを得ない。
Android: com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '~~~/jdk1.7.0_75.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1
Android アプリの開発をしているときに Android Studio を 2.1.0 から 2.2.0 にアップグレードした際に、Gradle ビルドで下記のエラーが発生しました。
com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '~~~/jdk1.7.0_~~.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
Android アプリの開発をしているときに Android Studio を 2.1.0 から 2.2.0 にアップグレードした際に、Gradle ビルドで下記のエラーが発生しました。
Unsupported method: AndroidProject.getPluginGeneration(). The version of Gradle you connect to does not support that method. To resolve the problem you can change/upgrade the target version of Gradle you connect to. Alternatively, you can ignore this exception and read other information from the model
はじめてまとも（仕事として）に iOS アプリの引き継ぎ開発をするにあたり、後方互換を意識しなければならず、Xcode プロジェクトのビルド設定にある Base SDK と Deployment Target の理解が曖昧だったので、公式ドキュメントを漁って調べてみました。
下記、公式ドキュメントをオレオレ和訳したものになります。
ご参考まで。
Xcode プロジェクトで特定の SDK を使うには、プロジェクトのビルド設定で 2 つの選択をおこないます。 これらの選択はプロジェクトで使う OS 機能を決定します。
Deployment Target はお使いのソフトウェアを実行できる最も古い OS バージョンを識別する設定です。デフォルトは Base SDK のバージョン以降に対応する OS のバージョンと同じです。 この設定のための Xcode ビルド変数名は MACOSX_DEPLOYMENT_TARGET (OS X Deployment Target) と IPHONEOS_DEPLOYMENT_TARGET (iOS Deployment Target) です。 Deployment Target 以前の OS に組み込まれている機能は無条件に利用できます。
Base SDK は Base SDK に対応するバージョン以前の OS に組み込まれている機能が利用できます。 この設定のための Xcode ビルド設定名は SDKROOT (Base SDK) です。 Deployment Target のバージョン以降、Base SDK に対応する OS バージョンまでの機能は、開発したアプリで利用できます。 ただし、新しい機能が使えるかどうかチェックする必要があります（「iOS 弱リンククラスの使い方」、「弱リンクメソッド、関数、シンボルの使い方」を参照）
以下、原文。
Base SDK and Deployment Target Settings
To use a particular SDK for an Xcode project, make two selections in your project's build settings. These choices determine which operating system features your project can use, as follows:
Choose a deployment target. This identifies the earliest OS version on which your software can run. By default, Xcode sets this to the version of the OS corresponding to the base SDK version and later. The Xcode build variable names for this setting are MACOSX_DEPLOYMENT_TARGET (OS X Deployment Target) and IPHONEOS_DEPLOYMENT_TARGET (iOS Deployment Target). You can unconditionally use features from OS versions up to and including your deployment target setting.
Choose a base SDK. Your software can use features available in OS versions up to and including the one corresponding to the base SDK. By default, Xcode sets this to the newest OS supported by Xcode. The Xcode build setting name for this parameter is SDKROOT (Base SDK). You can use features from system versions later than the deployment target—up to and including the OS version you've selected as your base SDK—but you must check for the availability of new features, as described in Using Weakly Linked Classes in iOS and Using Weakly Linked Methods and Functions.
For possible values and more information about build settings in Xcode, see Building for Multiple Releases of an Operating System in Xcode Project Management Guide, Xcode Build Setting Reference and Running Applications in iOS Development Guide.
When you build your application, your deployment target is reflected in the MinimumOSVersion entry in the application's Info.plist file. For iOS apps, the MinimumOSVersion entry is used by the App Store to indicate the iOS release requirement.
Figure 2-1 shows a timeline that explains the relationship between deployment target and base SDK.
The figure describes a project with a deployment target of OS X v10.4 and a base SDK of OS X v10.6. (The version numbers in the figure represent all releases of that version, including system updates.)
In this example, the software can freely use any features from OS X v10.0 through the newest update of version 10.4. It can conditionally take advantage of features from OS X v10.5 and 10.6, after ensuring that each such feature is available.
The effects of these settings at compile time and run time are as follows. If your code uses a symbol:
Not defined in the base SDK (for example, a symbol from a newer OS), you get a compile-time error. Defined in the base SDK but marked as deprecated, you get a compile-time warning. Defined in the deployment target, your code links and builds normally. At run time: On a system running an OS earlier than the deployment target, your code may fail to load if you use symbols unavailable in that OS. On a system running an OS equal to or later than the deployment target, your code has null pointers for symbols not available in that OS. Prepare your code for this as described in Using Weakly Linked Methods and Functions and Using Weakly Linked Classes in iOS.
Note: OS X v10.6 does not support using iOS Simulator SDKs prior to version 3.0. In addition, when building with Simulator SDKs, the binary runs only on the same operating system version as the base SDK, not on earlier or later versions.
Always check to see if you are using deprecated APIs; though still available, deprecated APIs are not guaranteed to be available in the future. The compiler warns you about the presence of deprecated APIs in your code, as described in Finding Instances of Deprecated API Usage.
When you change the base SDK setting, in addition to changing the headers and stub libraries your code builds against, Xcode adjusts the behavior of other features appropriately. For example, symbol lookup, code completion, and header file opening are based on the headers in the base SDK, rather than those of the currently running OS (if the two differ). Similarly, the Xcode Quick Help affinity mechanism ensures that documentation lookup uses the doc set corresponding to the base SDK.
In addition to setting the base SDK and deployment target for your project as a whole, you can set these values individually for each build target. Target settings override project settings. (However, some Xcode features that attempt to correlate with the base SDK setting, such as symbol definition and documentation lookup, may work differently.)
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
Jekyll: The 'pygments' configuration option has been renamed to 'highlighter'
ひさしぶりに Jekyll を起動したら、怒られてることに気付いた。
$ jekyll serve Configuration file: /path/to/project/_config.yml Deprecation: Auto-regeneration can no longer be set from your configuration file(s). Use the --[no-]watch/-w command-line option instead. Deprecation: The 'pygments' configuration option has been renamed to 'highlighter'. Please update your config file accordingly. The allowed values are 'rouge', 'pygments' or null. Source: source Destination: public Generating... done. Auto-regeneration: enabled for 'source' Configuration file: /path/to/project/_config.yml Deprecation: Auto-regeneration can no longer be set from your configuration file(s). Use the --[no-]watch/-w command-line option instead. Deprecation: The 'pygments' configuration option has been renamed to 'highlighter'. Please update your config file accordingly. The allowed values are 'rouge', 'pygments' or null. Server address: http://0.0.0.0:4000/ Server running... press ctrl-c to stop.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
