Eclipseのディレクトリの構成をAndroidStudioに変更するスクリプト

ディレクトリの構成だけ変更すれば、Android Studioからインポートすれば、そのまま開発を続けることができる。

gradle はデフォルトのwrapperで。問題あればAndroidStudioでいうところのモジュール内 build.gradle で調整していく。

なんせリソースディレクトリの変更をしておけば、今どきのAndroidStudioでは、設定等で対応。

sh(シェル)でやるけど、ディレクトリ構成の変更の内容は掴めるはず。

元々は、crashlytics がプロジェクトに反応しないのでやってみた。

続きを読む >>


AndroidStudio 0.2.13(Canary Build) で手動作業あります。

ゴツゴツと進むAndroidStudio。

0.2.13 へ更新です。

Android_Studio_Canary_Build_-_Android_Tools_Project_Site

Bug fixes:
The patch mechanism has been fixed (which prevented 0.2.12 from being sent out on the canary channel)
The Export APK dialog has been restored for Gradle projects (issue 60762)
The correct way to release an apk when using a Gradle project is to include your signing configuration inside your build scripts. This will allow you to properly sign the release versions of all the variants of your application by doing a "gradlew assembleRelease" from the command line.
We are working on coming up with a UI that achieves the same effect without having to edit the build.gradle files. (Issue 56532)
In the meantime, if you still choose to use the wizard, please make sure that you select a release version of your APK to sign and not a debug version.
From 0.2.12: The Breakpoints window does not work properly (issue 60721)
From 0.2.12: When using the Android Gradle plugin version 0.6.1, using JDK 7 in Studio does not work. ("Unable to find a JDK 1.6 installed", issue issue 60724)

Android Studio Canary Build - Android Tools Project Site

今回は?今回も?いろいろあります。

続きを読む >>


AndroidStudio 0.2.11 で リリースapkの署名ができない「Generate Signed APK」

ちっ、なんなんだよこれは。

build.gradle_-_Android_Studio__I_O_Preview__0.2.11

デバッグ版はエミュレータでも実機でも問題なく処理できますが。

Issue_60762_-_android_-_Problem_wen_generate_apk_-_Android_Open_Source_Project_-_Issue_Tracker_-_Google_Project_Hosting

Issue 60762 - android - Problem wen generate apk - Android Open Source Project - Issue Tracker - Google Project Hosting

ちっ。

対応方法を探します。

In the latest version of Android Studio (0.2.11) Generate Signed Apk no longer works. You're directed to set up a signing configuration in your gradle.bundle file, which (presumably) has to be run by hand from the command line unless you're willing to hardcode your password there

How to set up gradle and android studio to do release build? - Stack Overflow How to set up gradle and android studio to do release build? - Stack Overflow

I ended up just using "gradle installRelease" and coping the release APK from build/apk folder.
I am not sure why we are getting this, I do have my signingConfigs setup properly in build.gradle.

Android Studio: Signing issue after upgrade - Stack Overflow Android Studio: Signing issue after upgrade - Stack Overflow

android {
    signingConfigs {
        debug {
            storeFile file("debug.keystore")
        }

        myConfig {
            storeFile file("other.keystore")
            storePassword "android"
            keyAlias "androiddebugkey"
            keyPassword "android"
        }
    }

    buildTypes {
        foo {
            debuggable true
            jniDebugBuild true
            signingConfig signingConfigs.myConfig
        }
    }
}

Gradle Plugin User Guide - Android Tools Project Site Gradle Plugin User Guide - Android Tools Project Site

build.gradle を上記を参考に記述して、

$ gradle installRelease

と実行して、build/apk フォルダ内にapkを取ってきましたけど。

build.gradle にパスワードとかプレーンで書くとかどうなのか、
AndroidStudio のパスワード管理まわりが未対応なのかな。
(※ 再起動したらいけるときもあったりしたよ。)