以下是詳細的操作步驟：

第一階段：製作圓角效果 (圖片遮罩)

1. 點選圖片：按一下你要編輯的圖片。
2. 開啟裁剪選單：在工具列上找到「裁剪圖片」圖示旁邊的小箭頭 ▼ (滑鼠移上去會顯示「遮罩圖片」)。
3. 選擇圓角矩形：
   • 從選單中選擇 圖形 (Shapes)。
   • 選擇 圓角矩形 (通常在第二個位置)。
4. 調整圓角弧度 (重要)：
   • 圖片現在變成了圓角。你會看到圖片邊緣有一個小小的 黃色菱形 ◇ 控制點 (通常在左上角)。
   • 拖曳這個黃色菱形，可以調整圓角的弧度大小 (越往中間拉越圓)。

說明: 左上角有黃色的小點, 用來調整圓角長度.

第二階段：加入 #FA7070 顏色外框

1. 開啟框線顏色：
   • 保持圖片選取狀態，點擊工具列上的 框線顏色 圖示 (看起來像一支筆 )。
2. 新增自訂顏色：
   • 在顏色選單中，點擊 「+」 號 (在「自訂」標籤下方)。
3. 輸入色碼：
   • 在跳出的視窗上方欄位，輸入色碼 FA7070。
   • 按下 確定。
4. 設定框線粗細：
   • 此時框線可能太細看不清楚。點擊工具列上的 框線粗細 圖示 (三條線的圖示)。
   • 建議選擇 3px 或 4px 以上，這樣你的 #FA7070 顏色才會明顯。

快速套用格式：

如果你有多張圖片都要做一樣的處理，設定好第一張後，可以使用 複製格式 (Paint Format) 工具 (像油漆滾筒的圖示)，點一下第一張圖，再點第二張圖，就能瞬間套用圓角和粉紅框線了。

問題：違反不當廣告政策

您的應用程式內顯示的廣告除了必須符合我們的政策規定，還必須針對目標對象提供適當內容。舉例來說，如果應用程式的內容分級適用對象為未成年人，則不可放送含有兒童不宜內容或服務的廣告。

解法：

https://support.google.com/admob/answer/7562142?hl=zh-Hant&ref_topic=7384665

數位內容標籤

AdMob 會使用數位內容標籤，就廣告對不同目標對象的適合程度進行分級。這類標籤類似於其他機構組織為電影或電玩遊戲所設定的內容分級。

數位內容標籤依定義分為下列幾種：

• G：內容適合一般觀眾 (包括闔家皆宜的內容)
• PG：內容適合大多數的觀眾 (需有家長監護)
• T：內容適合青少年及較年長的觀眾
• MA：內容只適合成年觀眾

Google Play 和 Apple App Store 各有專屬的分級和標籤套用方式，用以判定內容對不同年齡層的適合程度。請參閱下表，瞭解您應用程式目標對象所對應的數位內容標籤。

程式：
provide targeting information to an ad request.

https://developers.google.com/admob/android/targeting#child-directed_setting

Bundle extras = new Bundle();
extras.putString("max_ad_content_rating", "MA");

AdRequest request = new AdRequest.Builder()
        .addNetworkExtrasBundle(AdMobAdapter.class, extras)
        .build();

 

完整範例：
https://github.com/googleads/googleads-mobile-android-examples/blob/master/java/advanced/APIDemo/app/src/main/java/com/google/android/gms/example/apidemo/AdMobAdTargetingFragment.java

App執行時遇到 Error:

consent form can be used with custom provider selection only.

或 Error:

consent form can be used with custom provider selection only.

這 2個都是因為選擇了 “Commonly used set of ad technology providers”.

According to documentation on Google Developers site:

Important: The Google-rendered consent form is not supported if any of your publisher IDs use the commonly used set of ad technology providers. Attempting to load the Google-rendered consent form will always fail in this case.

結論：the only case you can make use of Google-rendered form is use “Custom set of ad technology providers”.

解法 1號，選成 Custom 去挑 12個就可以了。

解法 2號，使用自己畫的 dialog, 這個解決會比較好，比較簡單，也可以解決  Consent SDK 翻譯的問題：

The Consent SDK allows to show a consent form which, however, it is currently in English only (version 1.0.3 of the SDK). SDK page says:

To update consent text of the Google-rendered consent form, modify the consentform.html file included in the Consent SDK as required.

解法 2號 URL:

https://stackoverflow.com/questions/50540538/gdpr-consent-sdk-consent-form-translation/50556255#50556255

解法 2號執行畫面：

原作者表示，可以使用他提供的 source code:

You are free to use my code, however consult your legal advisor, if the text is appropriate for you. I cannot provide legal advice on the consent text that is appropriate for you.

Add to your gradle file:

implementation 'com.google.android.ads.consent:consent-library:1.0.3'

Add member variables:

public boolean mShowNonPersonalizedAdRequests = false;
private AlertDialog mEuDialog;

In onCreate() call checkConsentStatus():

@Override
protected void onCreate(Bundle savedInstanceState) {
    // ...
    checkConsentStatus();
    // ...   
}

Add checkConsentStatus() method which uses Google’s Consent SDK:

// https://developers.google.com/admob/android/eu-consent
private void checkConsentStatus(){
    ConsentInformation consentInformation = ConsentInformation.getInstance(this);
    ConsentInformation.getInstance(this).addTestDevice("YOUR-DEVICE-ID"); // enter your device id, if you need it for testing

    String[] publisherIds = {"pub-YOUR-ADMOB-PUB-ID"}; // enter your admob pub-id
    consentInformation.requestConsentInfoUpdate(publisherIds, new ConsentInfoUpdateListener() {
        @Override
        public void onConsentInfoUpdated(ConsentStatus consentStatus) {
            log("User's consent status successfully updated: " +consentStatus);

            if (ConsentInformation.getInstance(MainActivity.this).isRequestLocationInEeaOrUnknown()){
                log("User is from EU");

                /////////////////////////////
                // TESTING - reset the choice
                //ConsentInformation.getInstance(MainActivity.this).setConsentStatus(ConsentStatus.UNKNOWN);
                /////////////////////////////

                // If the returned ConsentStatus is UNKNOWN, collect user's consent.
                if (consentStatus == ConsentStatus.UNKNOWN) {
                    showMyConsentDialog(false);
                }

                // If the returned ConsentStatus is PERSONALIZED or NON_PERSONALIZED
                // the user has already provided consent. Forward consent to the Google Mobile Ads SDK.
                else if (consentStatus == ConsentStatus.NON_PERSONALIZED) {

                    mShowNonPersonalizedAdRequests = true;

                    // The default behavior of the Google Mobile Ads SDK is to serve personalized ads.
                    // If a user has consented to receive only non-personalized ads, you can configure
                    // an AdRequest object with the following code to specify that only non-personalized
                    // ads should be returned.

                }


            } else {
                log("User is NOT from EU");
                // we don't have to do anything
            }

        }

        @Override
        public void onFailedToUpdateConsentInfo(String errorDescription) {
            log("User's consent status failed to update: " +errorDescription);
        }
    });
}

Add showMyConsentDialog() method:

public void showMyConsentDialog(boolean showCancel) {

    AlertDialog.Builder alertDialog = new AlertDialog.Builder(MainActivity.this, R.style.MyAlertDialogStyle);
    LayoutInflater inflater = getLayoutInflater();
    View eu_consent_dialog = inflater.inflate(R.layout.eu_consent, null);

    alertDialog.setView(eu_consent_dialog)
               .setCancelable(false);

    if (showCancel) alertDialog.setPositiveButton(R.string.dialog_close, null);

    mEuDialog = alertDialog.create();
    mEuDialog.show();

    Button btn_eu_consent_yes = eu_consent_dialog.findViewById(R.id.btn_eu_consent_yes);
    Button btn_eu_consent_no = eu_consent_dialog.findViewById(R.id.btn_eu_consent_no);
    Button btn_eu_consent_remove_ads = eu_consent_dialog.findViewById(R.id.btn_eu_consent_remove_ads);
    btn_eu_consent_yes.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            mEuDialog.cancel();
            toast(getString(R.string.thank_you), MainActivity.this);
            ConsentInformation.getInstance(MainActivity.this).setConsentStatus(ConsentStatus.PERSONALIZED);
            mShowNonPersonalizedAdRequests = false;
        }
    });
    btn_eu_consent_no.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            mEuDialog.cancel();
            toast(getString(R.string.thank_you), MainActivity.this);
            ConsentInformation.getInstance(MainActivity.this).setConsentStatus(ConsentStatus.NON_PERSONALIZED);
            mShowNonPersonalizedAdRequests = true;
        }
    });
    btn_eu_consent_remove_ads.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            mEuDialog.cancel();
            IAP_buyAdsFree(); // YOUR REMOVE ADS METHOD
            }
        });

    TextView tv_eu_learn_more = eu_consent_dialog.findViewById(R.id.tv_eu_learn_more);
    tv_eu_learn_more.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            euMoreInfoDialog();
        }
    });  
}

This is the consent layout, save to eu_consent.xml:

<?xml version="1.0" encoding="utf-8"?>
<ScrollView xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    >

    <LinearLayout
        android:id="@+id/ll_eu_consent"
        android:orientation="vertical"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:padding="@dimen/activity_horizontal_margin"
        >

        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:text="@string/eu_consent_text"
            android:textSize="14sp"
            android:paddingBottom="6dp"
            />

        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:text="@string/eu_consent_question"
            android:textSize="14sp"
            android:paddingBottom="6dp"
            android:textStyle="bold"
        />

        <Button
            android:id="@+id/btn_eu_consent_yes"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:text="@string/eu_consent_yes"
            android:textSize="13sp"
            />

        <Button
            android:id="@+id/btn_eu_consent_no"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:text="@string/eu_consent_no"
            android:textSize="13sp"
            android:layout_marginTop="6dp"
            android:layout_marginBottom="6dp"
            />

        <Button
            android:id="@+id/btn_eu_consent_remove_ads"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:text="@string/action_remove_ads"
            android:textSize="13sp"
            />

        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:text="@string/eu_consent_change_setting"
            android:textSize="14sp"
            android:paddingTop="6dp"
            android:paddingBottom="6dp"
            />

        <TextView
            android:id="@+id/tv_eu_learn_more"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:text="@string/learn_more"
            android:textSize="14sp"
            android:ellipsize="marquee"
            android:fadingEdge="horizontal"
            android:paddingTop="6dp"
            android:paddingBottom="6dp"
            android:textColor="@color/blue"
            style="@style/SelectableItem"
            />

    </LinearLayout>

</ScrollView>

Add euMoreInfoDialog():

private void euMoreInfoDialog(){

    AlertDialog.Builder builder = new AlertDialog.Builder(MainActivity.this, R.style.MyAlertDialogStyle);

    ScrollView sv = new ScrollView(this);
    LinearLayout ll = new LinearLayout(this);
    ll.setOrientation(LinearLayout.VERTICAL);

    LinearLayout.LayoutParams params = new LinearLayout.LayoutParams(
            LinearLayout.LayoutParams.MATCH_PARENT,
            LinearLayout.LayoutParams.WRAP_CONTENT);
    params.setMargins(40, 20, 40, 20);

    TextView tv_my_privacy_policy = new TextView(this);
    String link = "<a href="+PRIVACY_URL+">"+getResources().getString(R.string.app_name)+"</a>";
    tv_my_privacy_policy.setText(Html.fromHtml(link));
    tv_my_privacy_policy.setMovementMethod(LinkMovementMethod.getInstance());
    ll.addView(tv_my_privacy_policy, params);

    TextView tv_google_partners = new TextView(this);
    tv_google_partners.setText(R.string.google_partners);
    tv_google_partners.setPadding(40,40,40,20);
    ll.addView(tv_google_partners);

    List<AdProvider> adProviders = ConsentInformation.getInstance(this).getAdProviders();
    for (AdProvider adProvider : adProviders) {
        //log("adProvider: " +adProvider.getName()+ " " +adProvider.getPrivacyPolicyUrlString());
        link = "<a href="+adProvider.getPrivacyPolicyUrlString()+">"+adProvider.getName()+"</a>";
        TextView tv_adprovider = new TextView(this);
        tv_adprovider.setText(Html.fromHtml(link));
        tv_adprovider.setMovementMethod(LinkMovementMethod.getInstance());
        ll.addView(tv_adprovider, params);
    }
    sv.addView(ll);

    builder.setTitle(R.string.privacy_policy)
           .setView(sv)
           .setPositiveButton(R.string.dialog_close, null);

    final AlertDialog createDialog = builder.create();
    createDialog.show();

}

In your AdMob web interface select the ad technology providers you wish to use. I suggest you don’t select more than 20 (or so), because I assume the euMoreInfoDialog() will become very slow if you select too many providers.

Add to onDestroy() to prevent errors on screen rotate:

@Override
public void onDestroy(){
    // ...
    if (mEuDialog != null && mEuDialog.isShowing()) mEuDialog.cancel();
    // ...
    super.onDestroy();
}

When you make an ad request, check the value of mShowNonPersonalizedAdRequests and add "npa" to the request if necessary:

Bundle extras = new Bundle();
if (mShowNonPersonalizedAdRequests)
    extras.putString("npa", "1");

AdRequest adRequest = new AdRequest.Builder()
    .addTestDevice(AdRequest.DEVICE_ID_EMULATOR)
    .addTestDevice("YOUR-DEVICE-ID-GOES-HERE") // insert your device id
    .addNetworkExtrasBundle(AdMobAdapter.class, extras)
    .build();

And lastly, add strings for all your languages to strings.xml:

<!-- EU GDPR Consent texts -->
<string name="privacy_policy">Privacy Policy</string>
<string name="dialog_close">Close</string>
<string name="action_remove_ads">Remove ADs</string>
<string name="eu_consent_text">Dear user!\n\nWe use Google Admob to show ads. Ads support our work, and enable further development of this app. In line with the new European Data Protection Regulation (GDPR), we need your consent to serve ads tailored for you.</string>
<string name="eu_consent_question">Can your data be used to show ads tailored for you?</string>
<string name="learn_more">Learn how your data is used</string>
<string name="google_partners">Google and its partners:</string>
<string name="eu_consent_yes">Yes, continue to show relevant ads</string>
<string name="eu_consent_no">No, show ads that are irrelevant</string>
<string name="eu_consent_change_setting">You can change this setting anytime in the \"About\" window.</string>
<string name="thank_you">Thank you!</string>

That’s it!

(Note: log() and toast() are my methods, replace them with your own. PRIVACY_URL is your String url to your privacy policy.)

toast() 可以試看看這一組：

    public void toast(String text, Context context) {
        Toast.makeText(context, text, Toast.LENGTH_LONG).show();
    }

作者漏掉的 style

<style name="SelectableItem" parent="@android:style/Theme.Material.Light">
    <item name="android:background">?android:attr/selectableItemBackground</item>
</style>

Color:

<color name="red">#FF0000</color>
<color name="green">#00FF00</color>
<color name="blue">#0000FF</color>

相關範例：

• https://github.com/felixb/callmeter/blob/a51a0fe1a6bfcc4b72679f6add8c5ea7b51eae18/CallMeter3G/src/main/java/de/ub0r/android/callmeter/ConsentManager.java

shell script 很多，除了python 好用之外，常見的還有 unix 內建的bash shell script. 這次我選擇的是內建的，要用內建需要先學一下 bash shell 的 array 還有 loop 怎麼使用。

鳥哥loop 用法教學：
http://linux.vbird.org/linux_basic/0340bashshell-scripts.php#for

鳥哥array 用法教學：
http://linux.vbird.org/linux_basic/0340bashshell-scripts.php#array

接下來安裝 translate-shell
https://github.com/soimort/translate-shell

我是使用 Mac OS X, 需要另外再按裝 gawk, 只要使用指令：

brew install gawk

最後我的script 長醬子：

#!/bin/bash
filename="play_app_output.txt"
english="play_app_english.txt"
echo "" > $filename
cat $english >> $filename
echo "" >> $filename

function printit(){
	lang=${1}
	echo "<$lang>" >> $filename
	trans -b :$lang file://$english >> $filename
	echo "</$lang>" >> $filename
}

eat[1]="ar"
eat[2]="be"
max_nu=2

for (( i=1; i<=${max_nu}; i=i+1 ))
do
	printit ${eat[$i]}
done

要被翻的英文：

allow login facebook account by browser.

script 執行完的結果：

<en-US>

allow login facebook account by browser.

</en-US>

<ar>

.حفصتملا قيرط نع كوبسيفلا باسح لوخدلا ليجست حامسلا

</ar>

<be>

дазволіць уліковы запіс Увайсці facebook браўзэра.

</be>

後記：

bash shell script 寫起來是很快，也可以完成「大部份」的需求，但後來想用來解決 android strings 裡裡翻譯，bash shell script用起來綁手綁腳，限制太多，最後還是改寫成python…, 所以一開始就應該用python 寫，才省時間。

改用python，對字串和對檔案的處理就變的很簡單。執行外部指令可以使用：

from subprocess import call
tmp_input_file = "android_trans_input.tmp"
tmp_output_file = "android_trans_output.tmp"
trans_para_pattern = "trans -b -s en :%s -i %s -o %s" % (lang, tmp_input_file, tmp_output_file)
call(trans_para_pattern, shell=True)

我使用的副程式：

def google_trans(string_value, lang):
 tmp_input_file = "android_trans_input.tmp"
 outfile = open(tmp_input_file, 'w')
 outfile.write(string_value)
 outfile.close()

from subprocess import call
 tmp_output_file = "android_trans_output.tmp"
 trans_para_pattern = "trans -b -s en :%s -i %s -o %s" % (lang, tmp_input_file, tmp_output_file)
 #call(["trans", trans_para_pattern])
 call(trans_para_pattern, shell=True)
 #call(["ls", "-al"])
 #call("ls android_t*", shell=True)
 #call(["pwd"])

infile = open(tmp_output_file,"r")
 total_line = ""
 for in_line in infile:
 in_line = in_line.strip()
 total_line += in_line
 infile.close()

call("rm android*.tmp", shell=True) 
 return total_line

def convert_trans(filename, lang):
 #filename = "Localizable.strings"
 filename_ext = splitext(filename)[1]
 #filename_output = "%s%s" % (splitext(filename)[0], filename_ext)
 filename_output = filename
 directory_name = "./values-%s/" % (lang)
 directory_name = directory_name.replace("zh-", "zh-r")
 _createFolder(directory_name )

outfile = open(directory_name + filename_output, 'w')
 infile = open(filename)

total_line = ""

process_mode = "ios"
 if filename_ext == ".xml":
 process_mode = "android"

delimiter = "="
 if process_mode == "android":
 delimiter = ">"

string_pattern = '%s = "%s";\n'

for in_line in infile:
 out_line = in_line
 
 if is_translata_target(in_line, process_mode):
 # for translate item.
 if process_mode == "android":
 string_android_tag_name="string"
 if '</item>' in in_line and '<item' in in_line:
 string_android_tag_name="item"
 string_pattern = '%s>%s</'+ string_android_tag_name +'>\n'

string_key = in_line.split(delimiter)[0]
 string_value = find_between(in_line,">","</")
 string_value = encrypt_escape_word(string_value, process_mode)
 string_trans = google_trans(string_value, lang)
 string_trans = decrypt_escape_word(string_trans, process_mode, lang)
 out_line = string_pattern % (string_key.rstrip(),string_trans)
 #print out_line

if not is_skip_translata_key(in_line, process_mode):
 outfile.write(out_line)
 #total_line = u'%s%s' % (total_line,out_line)
 total_line += out_line
 infile.close()
 outfile.close()

心得是效果滿好的，還可以調整那些規則下的文字不要去翻譯。

如果你會處理到 lang=”ar” 或 lang=”fa”，記得要安裝一下 FirBiDi:

指令：

brew install fribidi

資料來源：

http://macappstore.org/fribidi/

• https://firebase.google.com/docs/admob/ios/quick-start
• https://developers.google.com/mobile-ads-sdk/docs/admob/ios/quick-start?hl=zh-tw

教學文章裡建議我們安裝CocoaPods, 安裝方法：

$ sudo gem install cocoapods

好像一行指令就結束了。

接下來去 Admob 建立一個 Project, 不到一分鐘就建立完了，比我打字還快！

https://apps.admob.com/

接下來要加入 Google Adsense

建立 Podfile

在與 BannerExample.xcodeproj 檔案相同的目錄中，建立一個檔案並將名稱設為 Podfile，其中包含以下項目：

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '7.0'

target 'BannerExample' do
 pod 'Google-Mobile-Ads-SDK', '~> 7.0'
end

Run pod update from the terminal.

執行完成後，關閉 BannerExample.xcodeproj 並開啟 BannerExample.xcworkspace。

標註成紅色，因為我開錯了，要開紅色這組。

發現無法Build, 有 Error, 所以對 BannerExample 專案按一下滑鼠右鍵，然後選取 [Add Files To “BannerExample”]。

然後再手動加入 SDK 需要的其他架構，包括：

AdSupport
AudioToolbox
AVFoundation
CoreGraphics
CoreTelephony
EventKit
EventKitUI
MessageUI
StoreKit
SystemConfiguration

為什麼需要自己手動加入這些 framework, 因為我開啟錯檔案，要開啟 .xcworkspace.

首先，我們要來拉 UI ，在 Storyboard。

Your first banner request

Now that you have a project with the SDK referenced, it’s time to put banner ads into it.

A GADBannerView can be created from storyboard or from code. Since layouts are generally defined in storyboard, this guide shows the storyboard method.

Add a GADBannerView in storyboard

Click the Main.storyboard tab. In the bottom-right corner, select a UIView element and drag it into your view controller. Then in the Custom Class section in the top-right corner, select the custom class GADBannerView as the Class for this view.

已經1年半沒寫iOS完全忘記怎麼插入View，紅色框框處是我找了一下終於找到的關鍵。

Add constraints on the GADBannerView

Set the following constraints on the GADBannerView:

• Locate it at the bottom of the screen.
• Set the size of the view to 320 wide by 50 high.
• Center it.

Make sure the view is selected, and click the Pin icon at the bottom of the screen. Add a Spacing to nearest neighbor constraint on the bottom of the banner with the value of 0. This pins the view to the bottom of the screen.

Also check the width and height constraints, and set the values to 320 and 50, respectively, to set the size of the view.

為什麼這裡是  320 x 50 px, 請參考看看 Google Ads 官方說明：
橫幅廣告大小
https://developers.google.com/mobile-ads-sdk/docs/admob/ios/banner?hl=zh-tw

其實，高度應該設90 或 100, 效果會比較好，預設的「智慧型橫幅廣告」可以套用到廣告比較多。

Adding a reference to your GADBannerView in code

The GADBannerView needs a reference in code to load ads into it. Open up the Assistant Editor by navigating to View > Assistant Editor > Show Assistant Editor. Make sure the ViewController.h file is showing in the Assistant Editor (the right pane of the screen). Next, holding the control key, click the GADBannerView (in the center pane), and drag your cursor over to ViewController.h (as indicated by the blue line going from the center pane to the right pane).

只記得要按Ctrl 去拉，但切到這個畫面預設是在 ViewController.m 拉半天都無法  Connect，原來是要再切到 ViewController.h.

似乎可以拉到 .m 檔案。

To resolve a compilation error, add @import GoogleMobileAds to ViewController.h or import GoogleMobileAds to ViewController.swift so the compiler knows that GADBannerView is a valid class.

Initialize the Google Mobile Ads SDK

At app launch, initialize the Google Mobile Ads SDK by calling configureWithApplicationID: in the application:didFinishLaunchingWithOptions:method of AppDelegate.m or AppDelegate.swift.

- (BOOL)application:(UIApplication *)application
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

  // Use Firebase library to configure APIs
  [FIRApp configure];
  [GADMobileAds configureWithApplicationID:@"ca-app-pub-3940256099942544~1458002511"];
  return YES;
}

這裡用的是Google Ads 給的第1組序號「應用程式 ID」，在 ViewController 裡用的是另一組「廣告單元 ID」。

修改 ViewController.m

- (void)viewDidLoad {
  [super viewDidLoad];

  NSLog(@"Google Mobile Ads SDK version: %@", [GADRequest sdkVersion]);
  self.bannerView.adUnitID = @"ca-app-pub-3940256099942544/2934735716";
  self.bannerView.rootViewController = self;
  [self.bannerView loadRequest:[GADRequest request]];
}

加好之後，按 Run 就成功了，廣告有出來。

Google Analytics可以幫我們網站分析：關鍵字、流量來源、瀏覽頁次，當我們有了這些數據，我們可以分析訪客習性、讀者喜歡看的資訊，透過有效的分析比對，可以幫助網站讓客人們更喜歡，而且這個Google Analytics 分析工具是完全免費的。

設定加入 Google Search Console 追蹤您的網站搜尋排名，並瀏覽更多網站管理員資源。
https://www.google.com/webmasters/

加入Google Search Console「可能」可以提高一點點在 Google Search 裡的排名，Google 在驗證 domain name 的擁有者時，有可能需要去設定一下自己的 DNS 增加一筆 TXT 的記錄，裡面放google 指定給我們的字串，用來證明我們是網域的擁有者。

上面這2個設定大約3分鐘就可以設好。

接下來要加入 Google Analytics (Google 分析)
https://www.google.com/intl/zh-TW_ALL/analytics/index.html

Google 分析畫面做的很怪，有點難以理解。要先點最左下角的齒輪（設定）然後在帳戶點下拉框，再「建立新帳戶」。

下一個步驟沒什麼難度，大約15秒就填完，Google 的設定就結束了。

回到 WordPress 裡，Google Analytics在WordPress官方外掛目錄中也是有非常多的應用外掛，我用的是：
Google Analytics for WordPress by MonsterInsights
https://srd.wordpress.org/plugins/google-analytics-for-wordpress/

MonsterInsights – Google Analytics Dashboard for WordPress (Website Stats Made Easy)

當然你也可以完全不去使用外掛，把 Google Analytics 提供的 javascript 放到自己的 html 裡就結束了，用這個  MonsterInsights 外掛有2個好處：

好處1: 自動幫我們取得我們Google Analytics  裡的設定值(Profile)，而且自動幫我們把 javascript 放到網頁裡。

這是 MonsterInsights 自動取得我們Profile 的介面。

好處2: 在我們的自己後台可以看到流量（PAGE VIEWS）、熱門頁面（TOP POSTS AND PAGES）、流量來源（TOP TRAFFIC SOURCES），訪客地區別（TOP COUNTRIES）。

流量在第1天是空白的，要過1天，才會跑出第1個小點點。

所有的設定5~10分鐘就設完了，WordPress 外掛下載和設定用不到1分鐘就設完了。

後來發現 googlebot 會來parse 443 port 裡的資料。所以我希望 404 錯誤的資料就從80 port 裡重新取得一次，丟給Google.

取得 ssl 憑證

首先，是 letsencrypt 的 certbot 的官方說明：
https://certbot.eff.org/#ubuntuxenial-other

照上面教學的指令下，只用一行就可以產生憑證。知道網站的根目錄用這行（指令1號）：

letsencrypt certonly --webroot -w /var/www/example -d example.com

如果你完全沒有網站，可以使用這行（指令2號）：

letsencrypt certonly --standalone -d example.com -d www.example.com

指令1號，letsencrypt 會放東西在 webroot 目錄裡，然後letsencrypt用 80 port 連回我們伺服器進去測試。

指令2號，會自動產生一個 80 port 的 service，然後letsencrypt用 80 port 連回我們伺服器進去測試。

這2個指令，都會因此去使用 443 port，實際上原理不需要了解太多，certbot 寫的滿聰明的，會在畫面上有提醒。產生完，手動測一下 renew，沒問題的把把 renew 指令放進排程裡。

letsencrypt renew --dry-run --agree-tos

成功後就會在ubuntu的/etc/letsencrypt/archive/ 下面看到憑證了。

在 80和443 port 都已經被其他程式使用中的請況下，需要更進階的設定，參考看看這一篇：

apache AH00171: Graceful restart requested, doing restart
https://stackoverflow.max-everyday.com/2017/02/apache-graceful-restart/

例如：

letsencrypt certonly --standalone -d example.com --tls-sni-01-port 445 --http-01-port 82

修改Tornado的 ssl_options

tornado改程式，須追加此兩個檔案的路徑在ssl_options下面，並注意檔案權限要能被讀。

http_server = tornado.httpserver.HTTPServer(Application(),
ssl_options={
“certfile”: “cert.pem”, #自行填好路徑
“keyfile”: “privkey.pem”, #自行填好路徑
})

完成之後，研究一下 tornado 的官方文件：
http://www.tornadoweb.org/en/stable/web.html#tornado.web.Application.settings

要使用下面的這組設定值來完成自動轉發：

• default_handler_class and default_handler_args: This handler will be used if no other match is found; use this to implement custom 404 pages (new in Tornado 3.2).

範例寫法：

import tornado.web


class BaseHandler(tornado.web.RequestHandler):
    """
    Base handler gonna to be used instead of RequestHandler
    """
    def write_error(self, status_code, **kwargs):
        if status_code in [403, 404, 500, 503]:
            self.write('Error %s' % status_code)
        else:
            self.write('BOOM!')


class ErrorHandler(tornado.web.ErrorHandler, BaseHandler):
    """
    Default handler gonna to be used in case of 404 error
    """
    pass


class MainHandler(BaseHandler):
    """
    Main handler
    """
    def get(self):
        self.write('Hello world!')

2. Settings. We need to define default_handler_class and default_handler_args as well

settings = {
    'default_handler_class': ErrorHandler,
    'default_handler_args': dict(status_code=404)
}

3. Application.

application = tornado.web.Application([
    (r"/", MainHandler)
], **settings)

as result. all errors except 404 gonna be handled by BaseHandler. 404 – ErrorHandler. that’s it

我的轉發的 code:

def write_error(self, status_code, **kwargs):
    if status_code == 404:
        from lib import libHttp
        http_obj = libHttp.Http()
        http_url = "http://%s%s" % (self.request.host,self.request.uri)
        (new_html_string, http_code) = http_obj.get_http_response(http_url)
        self.set_status(http_code)
        if not new_html_string is None:
            self.write(new_html_string)
        return
    return super(BaseHandler, self).write_error(status_code, **kwargs)

我最後放棄這個作法，改安裝 Nginx（發音同engine x）是一個網頁伺服器，它能反向代理HTTP, HTTPS, SMTP, POP3, IMAP的協議鏈接，以及一個負載均衡器和一個HTTP緩存。

https://www.nginx.com/resources/wiki/start/topics/tutorials/install/

範例：

nginx 基礎設定教學
http://blog.hellojcc.tw/2015/12/07/nginx-beginner-tutorial/

相關文章：

apache AH00171: Graceful restart requested, doing restart
https://stackoverflow.max-everyday.com/2017/02/apache-graceful-restart/

最佳的入門教學，應該是官方的這一篇：

Start Integrating Google Sign-In into Your Android App
https://developers.google.com/identity/sign-in/android/start-integrating

先 git clone 別人寫的範例，用修改會比較快：

https://github.com/googlesamples/google-services

github 的範例有一個問題，就是 apply plugin 是有問題的，改成這段就OK了。

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile 'com.android.support:appcompat-v7:24.2.0'

    // Dependency for Google Sign-In （這個版號，會一直被修改）
    compile 'com.google.android.gms:play-services-auth:9.8.0'
}

在修改時，和Facebook Login 最大的差別在Google Sign-in 不需要在 AndroidManifest.xml 裡增加一個 activity 的宣告。

Googe Sign-in 需要使用到一個「configuration file」，這是Facebook login 沒有的。

重新下載Google API 憑證，可以到這裡下載：

Google API Console
https://console.developers.google.com/

需要使用google token 來進行身分驗證，參考這一篇：

Authenticate with a backend server
https://developers.google.com/identity/sign-in/android/backend-auth

重點就是 android code 要多一行 requestIdToken：

GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
        .requestIdToken(getString(R.string.server_client_id))
        .build();

拿到token 之後，就可以連去google 問帳號資料：

https://www.googleapis.com/oauth2/v3/tokeninfo?id_token=XYZ123

If the token is properly signed and the iss and exp claims have the expected values, you will get a HTTP 200 response, where the body contains the JSON-formatted ID token claims. Here’s an example response:

{
 // These six fields are included in all Google ID Tokens.
 "iss": "https://accounts.google.com",
 "sub": "110169484474386276334",
 "azp": "1008719970978-hb24n2dstb40o45d4feuo2ukqmcc6381.apps.googleusercontent.com",
 "aud": "1008719970978-hb24n2dstb40o45d4feuo2ukqmcc6381.apps.googleusercontent.com",
 "iat": "1433978353",
 "exp": "1433981953",

 // These seven fields are only included when the user has granted the "profile" and
 // "email" OAuth scopes to the application.
 "email": "testuser@gmail.com",
 "email_verified": "true",
 "name" : "Test User",
 "picture": "https://lh4.googleusercontent.com/-kYgzyAWpZzJ/ABCDEFGHI/AAAJKLMNOP/tIXL9Ir44LE/s99-c/photo.jpg",
 "given_name": "Test",
 "family_name": "User",
 "locale": "en"
}

相關文章：

Integrating Google Sign-In into Your Android App
https://developers.google.com/identity/sign-in/android/sign-in?configured=true

Authenticating Your Client
https://developers.google.com/android/guides/client-auth

Add Google Sign-In to Your Android App
https://developers.google.com/identity/sign-in/android/

實作出來的範例：

Google 好心地提醒我們，別把user id 當參數傳給自己的後端server API, 而是要使用被驗證過的token.

Warning: Do not accept plain user IDs, such as those you can get with the GoogleSignInAccount.getId()method, on your backend server. A modified client application can send arbitrary user IDs to your server to impersonate users, so you must instead use verifiable ID tokens to securely get the user IDs of signed-in users on the server side.

https://developers.google.com/identity/sign-in/android/backend-auth

Verify the integrity of the ID token, 就把token 送 GET 到這個 URL:

https://www.googleapis.com/oauth2/v3/tokeninfo?id_token=XYZ123

If the token is properly signed and the iss and exp claims have the expected values, you will get a HTTP 200 response, where the body contains the JSON-formatted ID token claims. Here’s an example response:

{
 // These six fields are included in all Google ID Tokens.
 "iss": "https://accounts.google.com",
 "sub": "110169484474386276334",
 "azp": "1008719970978-hb24n2dstb40o45d4feuo2ukqmcc6381.apps.googleusercontent.com",
 "aud": "1008719970978-hb24n2dstb40o45d4feuo2ukqmcc6381.apps.googleusercontent.com",
 "iat": "1433978353",
 "exp": "1433981953",

 // These seven fields are only included when the user has granted the "profile" and
 // "email" OAuth scopes to the application.
 "email": "testuser@gmail.com",
 "email_verified": "true",
 "name" : "Test User",
 "picture": "https://lh4.googleusercontent.com/-kYgzyAWpZzJ/ABCDEFGHI/AAAJKLMNOP/tIXL9Ir44LE/s99-c/photo.jpg",
 "given_name": "Test",
 "family_name": "User",
 "locale": "en"
}