I'm trying to develop an app where you can send push notifications to the users with firebase cloud messaging.
I literally tried everything that i could find on the internet, but I doesn't seem to fix the problem. I compile using android 7.0 Nougat.
I already have this in my manifest file:
meta-data android:name="com.google.android.gms.version" android:value="#integer/google_play_services_version"
When I import google play services to my project, and build, this error appears.
Severity Code Description Project File Line Suppression State
Error No resource found that matches the given name (at 'value' with value '#integer/google_play_services_version'). firebaseTest C:\Users\andre\onedrive\dokumenter\visual studio 2015\Projects\firebaseTest\firebaseTest\obj\Debug\android\manifest\AndroidManifest.xml 14
This problem is really driving me crazy, and I would love if someone could help me solve it.
Thanks in advance!
Did you already get a chance to looking into doing it via azure?
https://learn.microsoft.com/en-us/azure/notification-hubs/xamarin-notification-hubs-push-notifications-android-gcm
I havent tried going direct to firebase but if you wanted to send messages via google messaging this is what I'd recommend.
Related
Please Help Me Fix this issue.
Recently when I updated my application(OXOO movies streaming app) I receive this email from Play Console:
Your app contains content that doesn’t comply with the Device and Network Abuse policy. We found your app is using a non-compliant version of an SDK which contains code to download or install applications from unknown sources outside of Google Play.
The SDK can be identified using the classname com.dcastalia.localappupdate.DownloadApk.
Affected Version(s):
App Bundle:3, App Bundle:3, App Bundle:3
But I have checked everything but have not found anything like this in the application.
Please give me some advice to fix this.
It is really important for me to release an update.
remove
implementation 'com.github.Piashsarker:AndroidAppUpdateLibrary:1.0.3'
from your build.gradle
I'm new to Android development, so I'm not familiar with the error message I'm getting. I need to control three on-board LEDs while using a recording app. I've researched two possible solutions.
The first was to look for other open source apps that control phone LEDs, but I couldn't find any open source apps to look at.
The next thing, and what i think is the more correct way, is using Android Things. As I understand it, I should be able to use the Things API in a full android app to control LEDs. I've followed the tutorial shown here: https://developer.android.com/things/training/first-device/create-studio-project
I'm sure I've followed the basic steps correctly which involves modifying the user libraries, editing the gradle file, and adding a GPIO permission. I've also confirmed this with multiple different Android Things Tutorials.
The problem I"m running into is that I'm getting this error:
Installation did not succeed.
The application could not be installed: INSTALL_FAILED_MISSING_SHARED_LIBRARY
List of apks:
[0] 'C:\Users\Richard\AndroidStudioProjects\LEDControl\app\build\outputs\apk\debug\app-debug.apk'
Installation failed due to: 'null'
I've tried seraching for solutions and the main one I Found was to add -r and -t as compile flags, but that didn't fix the issue.
I've looked at the logcat when trying to load the app on to my device, but I don't understand why I'm getting the not-found error:
2020-07-29 14:43:11.719 1833-1883/system_process W/PackageManager: Reconciliation failed...
com.android.server.pm.PackageManagerService$ReconcileFailure: Reconcile failed: Package com.example.ledcontrol requires unavailable shared library com.google.android.things; failing!
at com.android.server.pm.PackageManagerService.reconcilePackagesLocked(PackageManagerService.java:16752)
at com.android.server.pm.PackageManagerService.installPackagesLI(PackageManagerService.java:17113)
at com.android.server.pm.PackageManagerService.installPackagesTracedLI(PackageManagerService.java:16402)
at com.android.server.pm.PackageManagerService.lambda$processInstallRequestsAsync$13$PackageManagerService(PackageManagerService.java:14647)
at com.android.server.pm.-$$Lambda$PackageManagerService$S4WxZjKnT0iu1kmEXSrs7BiizN4.run(Unknown Source:6)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:67)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
I've also tried downloading the sample programs listed on the site, but they give me gradle build errors.
At this point, I'm not really sure what else to do and any help (including alterantive solutions for controlling on board LEDs) is much appreciated.
Thank you,
I am getting the following error when I attempt to compile in release mode to put my application in the Android App Store. I do not get the error when I compile for debug mode.
I have found references to similar errors. They seem to revolve around the android support services not matching the Android SDK. I am running on the Android 28 SDK. I have updated my google support libraries to the v28.0.0 in NuGet. I am running in macosx and am using vs mac.
I am quite at a loss on this issue. Any suggestions are appreciated.
TIA
...../obj/Release/lp/40/jl/res/values-v26/values-v26.xml(0,0): Error APT0000: Error retrieving parent for item: No resource found that matches the given name 'Base.V21.Widget.Design.AppBarLayout'. (APT0000)....
Ok, I'm not sure that I have "solved" the problem completely, but I have at least solved it for the moment. I kept digging into the output and found a funny character in the custom proguard.cfg information in the build output. I opened the proguard.cfg file that I had created in notepadd++. Sure enough, notepadd++ is set to encode with the "UTF-8 with BOM" setting. I changed that, resaved, rebuilt, and no errors. I'm going to keep a watchful eye on this, but the problem for the moment is resolved. Thanks for everyone's input. It was much appreciated. :-)
I have an App that uses Admod and Firebase from Google. Since I am using Swift they want me to use frameworks when loading them from CocoaPods. When I try to archive/validate the App I get the error:
No suitable application records were found. Verify your bundle identifier 'org.cocoapods.GoogleToolboxForMac'
What is the correct way to provision an app that uses someone else's frameworks so it can be uploaded to iTunes Connect? I tried to find something in Apple's documentation but I haven't found anything.
UPDate:
I previously had answered my own question, since I had thought I had found a solution. My reply was:
Problem Solved. Turns out I was using an App-ID that I am having Apple look into as being corrupt. I had already created a new App-ID to prove the one I want to use is not working and retried with that and it Validates. This required a lot of help from the Google Ads Mobile SDK team. Thanks.
So the correct answer is: Now Incorrect
You should not get this error unless you are using a Bundle-ID that is not already registered on iTunes Connect, but, you should never be able to create an archive that does not have a Bundle-ID that is not already registered on iTunes Connect. So this is caused by an abnormal situation.
This is no longer true
I used my new working project and got 4 whole builds out of it and into iTunes Connect. In the process I was trying to clean up the mess caused by trying to solve this problem, like loosing my git history. I tried to modify my old App to get it to work and without modifying my new working project, But my new project started failing with the above error. I even used my time machine and went back to the directory as it was when I made the last build, but no help. So, any answers?
Further Update:
I pulled all the code related to Google Firebase and Admob out of the code and removed the cocoaPods and Archived/Validated and now I get the error:
You must supply a CFBundleIdentifer for this request.
Which is the error message I was getting with my other App-ID that tracked that App-ID in iTunesConnect. This time it does not track the App-ID so it must be something in my project. Will report what I find.
UpDate:
I think Apple has been modifying their code for validation at the same time I was trying different things. At one point it told me I was using CFBundleSignature instead of CFBundlePackageType set to APP and I fixed this and got the code to validate. Understand I am copying complete projects and renaming everything to debug this problem, so this must have come from the original program. I ended up with a project that was renamed from my original but archived/validated but when I went to compile for Test I got errors that I debugged until I got lots of Mach-O link errors. I decided to complete the loop and go back to my original code and try using the new Bundle-ID which points to the new App-ID, the one that works, and add all the knowledge I have learned. But when I get it done I have an project that can test but does not validate. The only difference is this project has the old identifier which has the same name as the suffix of the App-ID that has a bug.
Am I missing something?
Final UpDate?
On a whim I renamed the Scheme file to be the same as my Suffix to the Bundle-ID and I got my original Project to Validate! I have worked on this for over a month and you might not believe the astonishment I feel in this.
Back to Unit Test!
I have come to the conclusion that the Identity of the App, the name at the far top of the right side Utilities window, has something to do with the way iTunes Connect validates the App. This is the name in the left hand column of the Organizer window. It is like it overrides the suffix of the Bundle-ID and since I can't use that Identifier because the associated App-ID is corrupt. Or the name of the Scheme.
I'm trying to port FirefoxOS on Motorola G but I don't understand how to write device manifest. What should be specified in the manifest? Where do I start? Mozilla's official documentation isn't that helpful actually.
The manifest is tricky but like a bike - one you get the hang of it then it becomes second-nature.
Here are the links I used to understand the manifest:
https://developer.mozilla.org/en-US/Apps/Developing/Manifest
https://developer.mozilla.org/en-US/Apps/Developing/About_app_manifests?redirectlocale=en-US&redirectslug=Web%2FApps%2FFAQs%2FAbout_app_manifests
The main point that helped me was to understand that only two fields are required: name, and description. This make other options specific to your needs, so I stripped all other members out to start: "locales" and "developer".
The primary config that I needed to get right was:
launch_path - I got it to work through trial-and-error, but then moved the app within my architecture and was surprised when the app went 404! I shouldn't have been surprised because... the path was incorrect. After updating the path the app installed correctly.
For example:
/Apps/App1/app1.html
Final bit of advice on Manifest. The best way to understand it is to get a test app working from the mdn-app-template! This way you can see how it works and test it's capabilities. I strongly recommend this as a first step. https://github.com/chrisdavidmills/mdn-app-template
Other suggestions:
- It took a while to get the workflow down. It is possible to just click a 'refresh' link in the App Manager. Which is a rather immediate workflow.
- Uninstalling in Android was weird. The app is actually saved within Firefox. So you have to go to about:apps to uninstall. Here is the link: https://developer.mozilla.org/en-US/Apps/Developing/Apps_for_Android
Hope it helps.