Why did crawling errors regarding App Indexing increase instantly? - android

we experienced an instant app indexing error increase from 0 to more than 100k. We cannot explain the spontaneous increase of errors especially cause each error refers to the HTTP schema of deep links that we do not support at all.
We have established a custom schema which is successfully online since years now. Strange thing is also that despite the error reports, the search traffic seems to be okay. It has not dropped since, what we would have expected if there is a real problem.
What is even more confusing is that the deep links generated by the SearchConsoles help page are faulty. Regardless that they are generated with the HTTP schema the generated ADB command is correct but the generated intent URL for browsers is defininetly wrong.
See this example for the site
http://www.finanzen.net/Kursziele/CEWE_Stiftung:
SearchConsole Help: intent://<OURPACKAGE>/http/www.finanzen.net/Kursziele/CEWE_Stiftung#Intent;scheme=android-app;package=undefined;end
Firebase TestConsole Help: intent://www.finanzen.net/Kursziele/CEWE_Stiftung#Intent;scheme=http;package=<OURPACKAGE>;end
So for the moment we suspect an update of SearchConsole to be responsible for this behaviour. If not we are completely puzzled.
Anyone else experiencing this?

I was seeing similar error reporting anomalies and reached out. I've heard from the App Indexing support team that this is a known issue and they are working on it. No ETA yet.
Copy of email from App Indexing support

Related

Firebase Crashlytics: Combine/Merge Similar Issues?

I had Firebase Crashlytics installed in my Android app, and the reporting is operational.
However, I found that some issues are very similar:
And it'd be helpful if I could treat them as the same issue when debugging or closing.
Is there any chances I can merge them into one?
It is not possible to merge these crashes. Crashlytics will group the issues based on the frame being blamed. In this case, even though they look similar, the frame is under a different line number.
You could file a feature request for this behavior.

INSTALL_FAILED_DEXOPT when using GreenDao

Background
I wanted to simplify the usage of DB in an Android app.
For this, I've compared some third party libraries that create a DAO layer.
I've come up with a nice library called "GreenDao" (presentation about it here) . The website shows that it's faster than other competitors (like ORMLite) and is optimized for Android.
The problem
For some reason, on some device (usually old devices, with GB) , I get the next console error when trying to install the app:
Installation error: INSTALL_FAILED_DEXOPT
Please check logcat output for more details.
Launch canceled!
I've searched for the reason of this error, but couldn't find out how to solve it. Many complain about this error, but I can't find out why it occurs, and what can be done.
The error is quite common and known, but it's never mentioned as the result of using this library, yet when I remove the usage of this library, everything works fine...
Also note that on newer devices (like nexus 4) it installs and works just fine, and that the sample itself also works fine no matter which device I test it on.
The question
Why does it occur?
Is it possible that the structure of the classes is just too much for old devices to load, since we use other libraries ?
Could it be that I've reached the limit of code that is supported by android apps?
The jar file itself takes just 87KB ...
How can I solve this?
Ok, I've found the problem and the solution:
It has nothing to do with GreenDao.
It's because the app uses too many jars, so maybe Android has a limitation of code.
The solution is to either delete un-needed jar files or delete a lot of code.

Admob - can't create any ads (admob wizard crappy?)

I'm trying to create some ads in Admob, but on last step I always get error:
There were problems with your submission
but it didn't specify WHERE. I swear god, there are no errors on whole page, all fields are correctly filled, I see no red shapes around fields, everything match criterias written under fields, but I stil get this error - without any explanation. Has anybody same experiences? It's totally frustrating :(
Ok, it was google's fault - after 3 hours of trying I just let it go, and on the evening of same day I tried just save it again (with no changes) - and it suddently worked. I wrote to google about this mystery, but (again) without success.
However I must (again!) strongly criticize google, their admob wizard is crappy, this was not the first problem I had. Next few days I had many many problems with my ads - they approved my ad, and when I copied it (without changes) it was dissaproved. After 2-3 times save it was approved. Like random behaviour, or I don't know what is it.
Conclusion: I can't understand how such big company can have such LAME LAME LAME errors on their sites, in admob, in android sdk, in their docs, in their support teams (which mostly don't answer) etc...Google, wake up!!!
I had the same problem while using lates Google Chrome... Then I tried FireFox and everything worked fine.
Very strange ;-)

Facebook login keeps failing

Before starting, a very similar question was asked recently, but I was facing a couple of other issues, and wanted to add some context.
Basically, off late, I witnessed that the login with Facebook feature in my Android app would keep failing for new users (who hadn't authorized the app before). However, this wasn't a recurring issue, so I sort of ignored it. But now this seems to be happening far too regularly.
I am absolutely sure that no changes were made in the app's settings locally or with the FB settings page.
There are 2 variants of the error -
a simple "Error occurred. Try again." And another which gives a much more detailed output.
>>>>>
However, I'm not sure of what changes do I need to make, if any. Would really appreciate any help with this.
Thanks.
In your facebook developer account try going to your application settings-> advanced and select Native/Desktop in Authentication. This should remove at least the first error.
I created a new application today and I'm also facing the second error. But for the older projects it works.
A bug report for this had been filed, and it has been closed now.

Google IO Twitter Livefeed from a fresh install

I just dowloaded the Google IO Source code from here: http://code.google.com/p/iosched/ in order to understand the great UI of this app.
I also wanted to grab the code of the Twitter LiveFeed, but when compiling freshly downloaded code, I get a crazy UI:
I don't understand what's wrong as I didn't changed one line of the code!
Does this issue happens on other people devices?
Thank a lot.
I answer myself in case other people also searching for the answer:
http://twitter.com/#!/romannurik/statuses/69818965840506880
yes we used some custom Google
Realtime Search tweaks that I
explicitly removed from open source.
So that seem impossible for now... Or we will have to look for other alternatives

Categories

Resources