"Seeking Help with AppWrite Integration for Android: Manifest Issues and Reverse Engineering Concern
Good evening everyone.
To get the elephant out of the room, I'm definitely doing something wrong here. Apologies for the silly question...
I'm trying to start with AppWrite for my first Android application. I followed the documentation for user authentication. (https://appwrite.io/docs/quick-starts/android)
Initially, the following block of code in the manifest doesn't work for me:
<activity android:name="io.appwrite.views.CallbackActivity" android:exported="true">
<intent-filter android:label="android_web_auth">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="appwrite-callback-111111111111111" />
</intent-filter>
</activity>
And in order to connect to the database and create my first user, I had to write the following:
<meta-data
android:name="KEY_APPWRITE_API_ENDPOINT"
android:value="https://cloud.appwrite.io/v1" />
<meta-data
android:name="KEY_APPWRITE_PROJECT_ID"
android:value="111111111111111" />
I’m not sure if this is correct, but this is how I managed to address the "Expected URL scheme 'http' or 'https' but no scheme was found for null/a..." issue. <meta-data android:name="KEY_APPWRITE_API_ENDPOINT" android:value="${KEY_APPWRITE_API_ENDPOINT}" />
<meta-data android:name="KEY_APPWRITE_PROJECT_ID" android:value="${KEY_APPWRITE_PROJECT_ID}" />
Also, is it okay for reverse engineering purposes to have these values in the manifest? I tried to retrieve the values from local.properties but didn't succeed.
<meta-data android:name="KEY_APPWRITE_API_ENDPOINT" android:value="${KEY_APPWRITE_API_ENDPOINT}" /> <meta-data android:name="KEY_APPWRITE_PROJECT_ID" android:value="${KEY_APPWRITE_PROJECT_ID}" />
Thank you very much for your time.
Please use triple backticks for longer code blocks
Hello World!
// Hello World!
