Twitter issues in old project - android

Yesterday I got one old project when i am trying to compile the project i get following error
Attribute is missing the Android namespace prefix in
<activity android:name="net.mxxxx.xxxxx.twitter.AuthTwitter" android:launchMode="singleTask" android:screenOrientation="portrait">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data host="twitterAuth" android:scheme="xxxxxx" />
</intent-filter>
</activity>
Minimum SDK was "7" i made it up to 13 , Please help why error is occurring

The real question is why it wasn't complaining before. Just change this:
<data host="twitterAuth" android:scheme="xxxxxx" />
to
<data android:host="twitterAuth" android:scheme="xxxxxx" />

Related

Deeplink errors displayed on Google Console different from in AndroidManifest.xml

My app shows errors with a deeplink in Google Play Console:
In which the failed link was "https:///"
In the AndroidManifest.xml has this configuration:
<activity
android:name=".AppLinksActivity"
android:resizeableActivity="false"
android:exported="true"
android:launchMode="singleTask">
<intent-filter android:autoVerify="true">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data
android:scheme="https"
android:host="your_game_domain.extads.gl.com"
/>
</intent-filter>
</activity>
The other link works just fine. I don't know where the triple dashes in the faulty link come from.
Could anyone help me find the causes and how to fix this? Much appreciated.

Firebase crashlytics error with msal library in android manifest

I have weird issue happens only on one phone, but it application was working for months on this phone Samsung Galaxy s8 for a long time. Reinstalls doesn't give the solution. Install previous version doesn't work as well. It works on other phones. What happens, how to fix it?
error from crashlytics:
Fatal Exception: com.microsoft.identity.client.exception.MsalClientException
Intent filter for: BrowserTabActivity is missing. Please make sure you have the following activity in your AndroidManifest.xml <activity android:name="com.microsoft.identity.client.BrowserTabActivity"> <intent-filter> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <data android:host="com.example.deepdiveandroid" android:path="mypath" android:scheme="msauth" /> </intent-filter> </activity>
com.microsoft.identity.client.PublicClientApplicationConfiguration.checkIntentFilterAddedToAppManifestForBrokerFlow (PublicClientApplicationConfiguration.java:591)
My androidmanifest.xml
<activity
android:name="com.microsoft.identity.client.BrowserTabActivity">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data
android:scheme="msauth"
android:host="com.example.myname"
android:path="/M41ng+ad69kgXmsY1eacX8frPLy=" />
</intent-filter>
</activity>
*it happens after just open the app
**path is changed to random, normally it is different.

assetlinks domain vs host

I am trying to setup applinks in my android app. In my manifest file I have something like this:
<intent-filter android:autoVerify="true">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data
android:scheme="https"
android:host="myapp.example.com" />
</intent-filter>
So my question is where EXACTLY will the app try to download the assetlinks.json file:
a - https://myapp.example.com/.well-know/assetlinks.json
b - https://example.com/.well-know/assetlinks.json
c - https://www.example.com/.well-know/assetlinks.json
Thanks for your help
According to this Google Guide, it'll try to download from:
https://myapp.example.com/.well-known/assetlinks.json

Android : Paypal Express checkout integration not working

I am integrating paypal express checkout to my android studio project.
Added dependencies compile 'com.braintreepayments.api:braintree:2.+'
Added below code in manifest.xml
<activity android:name="com.braintreepayments.api.BraintreeBrowserSwitchActivity"
android:launchMode="singleTask">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="${applicationId}.braintree" />
</intent-filter>
</activity>
Finally calling paypal fragment using below code
BraintreeFragment mBraintreeFragment = BraintreeFragment.newInstance(PayActivity.this, tokenValue);
PayPalRequest request = new PayPalRequest(amount.getText().toString())
.currencyCode("USD");
PayPal.requestOneTimePayment(mBraintreeFragment, request);
But the app is not redirecting to the paypal screen.
Can you guys please let me know what else i need to do to achieve this.
Thanks.
<activity android:name="com.braintreepayments.api.BraintreeBrowserSwitchActivity"
android:launchMode="singleTask">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="com.myhomework.myhomework.braintree" />
</intent-filter>
</activity>
your data android:scheme = should be equal to ua package name.braintree.. and if your packagename or package id has capitalised letters please use small

Android Dropbox SDK manifest setup

Any ideas why I get this error when I call getSession().startAuthentication() for the Android Dropbox SDK?
: FATAL EXCEPTION: main
: java.lang.IllegalStateException: URI scheme in your app's manifest is not set up correctly. You should have a com.dropbox.client2.android.AuthActivity with the scheme: db-CHANGE_ME
Yet my AndroidManifest.xml has the following within the <Application></Application> as instructed in the getting started instructions.
<activity
android:name="com.dropbox.client2.android.AuthActivity"
android:launchMode="singleTask"
android:configChanges="orientation|keyboard">
<intent-filter>
<!-- Change this to be db- followed by your app key -->
<data android:scheme="db-MYKEYISHERE" />
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.BROWSABLE"/>
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
If you're actually seeing "db-CHANGE_ME" (i.e. that's not a placeholder you used to obscure your app key), then it means you haven't updated the app key in the Java code of your app. That error message outputs the key which was provided in the Java code, and expects it to match the key in the manifest.
Your clean build might've picked some Java changes which weren't previously built.
For those facing this problem, if you're like me you might not pay attention to a little detail, take a look at your manifest:
<intent-filter>
<data android:scheme="db-APP_KEY" />
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.BROWSABLE" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You shouldn't replace the whole string db-APP_KEY with your app key, you should leave db- there db-{HERE YOUR APP KEY} I know I know, it took me a while to figure out this.
Example:
<intent-filter>
<data android:scheme="db-hafsa324dasd" />
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.BROWSABLE" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
When I copied the App_ Key I forgot to add the 'db' part to my answer.
Example:
<data android:scheme="db-APP_KEY" />
Should be :
<data android:scheme="db-hafsa324dasd" />
Should Not Be :
<data android:scheme="hafsa324dasd" />
No idea why this should be the case but a project clean did the trick (I added the code to the manifest days ago and cleaned several times since)

Categories

Resources