When my app checks for obb expansion file it crashes, giving the following error:
Service Intent must be explicit: Intent { act=com.android.vending.licensing.ILicensingService } - Error.
I know that this exact issue was a problem on Android 5.0+ and it was solved as follows:
https://code.google.com/p/android-developer-preview/issues/detail?id=1674
However, this is happening again on android 6.0+ now. And that fix is not working for 6.0+.
Any idea how to solve this?
Related
this isn't directly a question about android development, but about how to file a bug report if you found a bug within the android OS.
I have seen this documentation link: https://source.android.com/docs/setup/contribute/report-bugs
which finally leads to this bug-tracking system:
https://issuetracker.google.com/issues?q=status:open%20componentid:190923
I created a bug report there, however, after creating it I get an error message saying:
New issue created: 259508180 (view access not granted)
Am I missing something? Thanks in advance for the help!
I have a Xamarin for Android app that has been working until today. I needed to make a change but before I did, I ran a test to ensure no VS or Nuget package updates caused an issue. I have Xamarin.Essentials in my app and this line worked before, not sure what is happening now.
if(DeviceInfo.Model == "TC72"){scannerIndex = 1;}
Exception Unhandled:
Xamarin.Essentials.NotImplementedInReferenceAssemblyException: 'This
functionality is not implemented in the portable version of this
assembly. You should reference the NuGet package from your main
application project in order to reference the platform-specific
implementation.'
Any insight would be helpful. TIA
I changed the DeviceInfo.Model to Build.Model and get the same info I was expecting. That fixed my issue. If anyone has a different suggestion, happy to entertain them.
Added 8/11/21 3:25pm CT
I also found that changing my Compile Target to 10.0 fixed the Xamarin.Essentials issues. So far the application is working on 8.1 on the device (Zebra MC3300).
My exoplayer2 is working fine in devices like Samsung, Motorola, Xiomi, sony etc on both release and debug build.
But when I have released my app on play store, it is throwing error on devices like nexus 4(Android version 6.0.1) and some Vivo models like Vivo Y53, Y71, and V5 having android version 6.0.1, 7 and 8.
Crashlytics showing this error : Caused by android.view.InflateException: Binary XML file line #153: Error inflating class com.google.android.exoplayer2.ui.PlayerView
My code already contains properties mentioned in Error inflating class com.google.android.exoplayer2.ui.SimpleExoPlayerView but still facing issue in few devices.
Can it be because of custom ROM in Vivo and Nexus devices?
Found solution for this, it was not any development error because if it would have been any code error, then it should have occurred on multiple devices.
So, my last resort was to rectify what exactly is happening. As the app's apk was uploaded as a bundle, then if the user was installing the app after sharing the bundle apk (sideloading) by ShareIt or Whatsapp, it was getting crash, because it is app bundle's property that we cannot share the APK generated from bundle.
So, to check that if user is installing the app through sideloading, we can add google's play core library to let them know that the "app is missing components. Please install from playstore".
Gradle:
implementation 'com.google.android.play:core:1.6.3'
Application Class in onCreate():
if (MissingSplitsManagerFactory.create(this)
.disableAppIfMissingRequiredSplits()) {
return;
// Skip app initialization.
}
As per the Documentation, please add below lines in build.gradle(Module:app)
compileOptions {
targetCompatibility JavaVersion.VERSION_1_8
}
Hope this helps.
I am an experienced Java programmer just starting out with Android development. I am going through the tutorials and am having a problem with the tab widget tutorial. I have followed the example to the letter and keep getting the below in the log when trying to run on the emulator:
ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.android/.HelloTabWidget }
ActivityManager: java.lang.SecurityException: Permission Denial: starting Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.android/.HelloTabWidget } from null (pid=-1, uid=-1) requires null
I have searched the internet forums for the last three hours and can't find any answers to what is going on. The tutorial I am using is here: http://developer.android.com/resources/tutorials/views/hello-tabwidget.html. I am using jre 1.6, and Android platform 2.1. Any help will be appreciated. I can't tell you how frustrating it is when you follow a supposed simple example and you can't get it to work.
If you are still having issues and you have tried all that is mentioned above...
Last try is:
Make sure your target SDK and ADT matches the required SDK and ADT version...This will surely help. My project is looking for API 8 and I have API 14. So I have installed API 8 version with ADT8.X version...
Without having done this particular tutorial, I'll say that the main reason for permission denial errors in Android in my limited experience is failure to declare necessary permissions in the AndroidManifest.xml file. I'm not sure that this is the case here though.
This may be a red herring, but the name of your application doesn't look right. It looks like you've named it as if it's an android system application (the package prefix "com.android" I've only seen with regard to Android system apps). Maybe if you tried putting something other than "com.android" for the package field in your project this might help, because it could be that the namespace is protected.
When trying to run my application on the emulator I get an error from the activitymanager:
ActivityManager: Error type 3
My activity exists, is listed in the manifest (in fact, its the MAIN launcher activity).
Anyone know what this error means?
If you are running Eclipse try Projects-->Clean... and clean the project before running again.
i faced the same issue. I cleaned the project and removed the android:enabled=false in android manifest. This solved the issue.
Check "android:installLocation" in your AndroidManifest.xml.
"preferExternal" will cause the problem.
I got this error because I used invalid characters in my project name and Android didn't warned me about it so I had no idea that was the problem...
Example: "Thís ís íncorrect!"
nothing to worry about that it happens sometimes when activity manager unable to find activity of your app that means your target that is emulator is not started yet or may be because of following reason:
when you try to run your app on emulator you may be cancled in between building or forcefully closed your emulator.In that case when try to start emulator again it will sometimes not maximized.
now you have to restart your eclipse and then launch emulator and run your app now you will not face this type of error
Dont remember how I fixed this - most probably I wiped the local copy and re-checked out of svn.
ActivityManager: Error type 3
I don't know how true it is, but I used the same shared preferences file from another app..and got this error. I chose a new name for the shared preferences and the problem has gone away. It's working now
I had not enough space on my phone, that's why I had this problem.
So I cleaned it and go RUN )
I got this error when I mistakenly added a second application tag in my manifest as I was trying to add hardware acceleration to my app:
<application
android:hardwareAccelerated="true" />.
I added it above my actual application tag and I think this resulted in Android deploying an empty 'app' to my phone. It reported 'Installation success' in the logs and yet there was no launcher icon. It did appear, though, under Settings -> Apps but the only thing I could do there was to uninstall it. Hope this helps someone.
Thus, it seems there can be many reasons to see this error.
For those who can't fix it using the above mentioned methods:
In my case, i renamed the name of my activity (using F2 in Eclipse) and it is fixed.