Phileo

what would be the problem with/disadvantage to calling PdfView.fromAsset(pdfName).load() from within a BroadcastReceiver that was registered to listen for DownloadManager.ACTION_DOWNLOAD_COMPLETE as opposed to writing code from scratch to load the...

If you goto https://console.developers.google.com/apis/api/androidcheck.googleapis.com/overview and select your project in the upper left, you will see under the "Errors" section an http error code. In my case, I got a 403,...

@mcyrulik as a possible workaround, you could register an onItemSelected() listener to show a Crouton / Toast of the full text.

does anyone know any of the history and background of the problem with scanning the expiry date? Scanning expiry date was added in [V5.0.0](https://github.com/card-io/card.io-Android-SDK/releases/tag/5.0.0), which was over 2.5 years ago....

This SDK is no longer being actively maintained. Therefore, there is no fix for the expiry date issue (or any other issue) because of this. https://github.com/card-io/card.io-Android-source/issues/136

> Ok, if you need to render map without having a view, you would probably need to make a custom `MapView` class. On the positive side, the class can be...

> Collections.sort(arrEEGGraphEntries, EntryXComparator()) > > I apply this code but receive this error again and again @Mukesh9166 Does [com.github.AppDevNext:AndroidChart:3.1.0.21](https://github.com/AppDevNext/AndroidChart?tab=readme-ov-file#gradle-setup-with-jitpackio) fix your issue?

Similar Exception: Caused by: java.lang.IllegalStateException: Resolving configuration 'androidTestAnnotationProcessor' directly is not allowed at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.assertResolvingAllowed(DefaultConfiguration.java:888) at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.resolveToStateOrLater(DefaultConfiguration.java:434) at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.access$1600(DefaultConfiguration.java:114) at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationResolvableDependencies.getResolutionResult(DefaultConfiguration.java:1026) at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationResolvableDependencies_Decorated.getResolutionResult(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)...

I am experiencing this problem as well. The config file `proguard_annotations.pro` was supposed to provide the correct ProGuard config. However it is not working at least not on v2.0.1 AAR....

It appears to me that the check for Google Play Services is already done (indirectly) by `SimpleGcm.init()`, so that `init()` call just needs to inform the user and also prevent...