I am trying to add Admob Ads to Xamarin.IOS but i am unable to figure out way to achieve this goal.I have already searched internet but couldnt find the solution
Google Admob is available in Xamarin.iOS .
1.install the package Xamarin.Firebase.iOS.AdMob from nuget.
2.Registring with AdMob
So, the first thing that you will need to do is actually register for AdMob. This is the same thing that I did in Android, but I created an iOS project. This will give you two important pieces of information, your “Application Code” and your “Ad Unit Id”. We will use these later, but simply go to: https://apps.admob.com, register for a new app, link to an app in Firebase, and you will be off running.
3.Add GoogleService-Info.plist
When you create the new app in Admob/Firebase there will be a Google Service config plist file that gets downloaded. Add this to the root of your iOS project and make sure that the Build Action is set to BundleResource. This is super important!
4.Update AppDelegate
MobileAds.Configure("Your Publishing App Id");
You can ask for more details about Admob . And here is a sample that you can refer.
Related
I have already published my app on the playstore with keytore as .apk I am used to. But because of google notice that publishing App as APK will be obsolete in few months to come.
So, in a new upgrade of my app, I wish to upload it as app bundle. So while generating signed App bundle, with my app's keytore, I discovered that it generated the app bundle as (app-release.aab) and exported another key as private_key.pepk So when i revisited playstore console to upload the signed app bundle, I didn't see where to upload private_key.pepk.
So, I became worried. Not knowing what to do. I don't want to make a costly mistake. That is why I'm here for you to give me step by step method on how to continue from where I stopped.
Thanks for helping me..
EDIT:
I clicked create new release and then I clicked on opt in but didn't know which option to choose and proceed
Opt in to Play App Signing
Export and upload a key from Android Studio
Export and upload a key from Java keystore
Export and upload a key (not using Java Keystore)
I specifically need help getting the app build into my apps. I am so new to the MAC ecosystem. I need to get my app build from my windows 10 box (parallels) running VS2017/Xamarin Forms project uploaded to My Apps. What i have found is helpful if you are using xcode on the mac.
I have read tons of pages and help files and with all of that what I have includes:
created an app in VS2017/Xamarin that runs happily on the emulator from the MAC (MacBook Pro)
purchased the app dev subcription from apple
created a Production certificate (I don't need this yet but I was in there so...)
created a Development certificate
created a key pair from the Dev cert (that show up in the keychain)
created an App Group
created my app's placeholder under My Apps on App Store Connect
added my iPhone to devices via connecting to the Mac getting the UDID from iTunes
created a development provisioning profile for my iPhone (Not sure how this helps my testflight plight)
Assumptions
You must submit for review the same way for both TestFlight and Prod release to the actual store.
You don't need to open the app in xcode outside Xamarin
There is a tool or concept I am missing out on.
For development outside of Xcode, you will want to use Apple's Application Loader App to upload your app to App Store Connect.
As I said in comment to Matt below his correct answer to my actual question above, I needed to get the project right to get to that point.
Here are the more intimate details for the lurkers. I hope this helps some of you.
I was getting, or trying, to get all of this in place manually instead of letting VS do it's work getting this stuff together while I got to coding. FastLane FTW
Open the account management window, go to Tools > Options > Xamarin > Apple Accounts
Add your AppleID
Click on your appleID
Click the add button
Select your id in the lower text area
then add your distro cert. As is proper you deploy to TestFlight as a prod release.
Then get over to to your iOS project properties:
Make sure that your project is outputting an IPA. (Not Beer ;) )
These are my settings that worked. There could be other configurations that work as well.
I never get the automatic provisioning to work. And while this bundle signing settings look like it will not work, it does. I have received my apple approval for beta and users are in testflight.
Also, make sure you update the version of the app in the plist for subsequent releases. This change is not carried through from the AssemblyInfo.cs as one might expect. viola.
If you see this during debug make sure your debug version has Developer (Automatic) set for your debug settings.
FWIW - My VS2017:
While this does not perfectly match the info # https://learn.microsoft.com/en-us/xamarin/cross-platform/macios/apple-account-management?tabs=windows it worked for me. That page was key to the solution and deserves citing. Your mileage may vary.
If I missed something please reach out and I will update this.
I have xamarin project that someone developed it , and my task is to upload this project to appstore and play store .
i just have an Apple Developer Account and Apple ID Account
i saw this link according appstore in xamarin documentation https://developer.xamarin.com/guides/ios/deployment,_testing,_and_metrics/app_distribution/app-store-distribution/itunesconnect/
but i don't know if it's missing something or no or if this is the right link to follow !!
could anyone help me how to do this task step by step or any link that support that?
Yes you have found the Xamarin walkthrough that is the correct process for publishing to the Apple App Store.
There are a lot of steps and you have to follow them carefully.
The Android process is a lot simpler and can be found here
I'm working on the iOS 10 APNs function, trying to add Notification Service Extension to an existing App, add the function of pushing an image to the App.
After the extension was added, it did receive the pushed message. But couldn't receive the image, the function(wrote in the extension) of downloading the pushed image didn't execute during debugging. I checked the content in the App package, confirmed that the extension was installed in the App, it just didn't work.
What made me confused was that: I built a new testing project with same bundle id. The testing app could receive the pushed message and show the image correctly.(please see below screen shot)
What's wrong with the existing project? I tried to find the difference between the existing project and the testing project, yet found nothing in the code, setting, environment.
Does anyone encountered this before? I have been struggling in this for a week...
reference:
WWDC 2016 APNS Guide: https://willowtreeapps.com/ideas/wwdc-2016-rich-notifications-in-ios-10
Apple notification guide:https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ModifyingNotifications.html#//apple_ref/doc/uid/TP40008194-CH16-SW1
Finally this bug was fixed, please see the attached image. XCode recommends setting the architecture as automatic and I did so, then the notification service extension worked and could receive the pushed image. I don't know why this setting caused the problem, but I'm sure it works.
I am trying to submit my WatchKit app t iTunesConnect. I click "Archive" and then validate and I am shown the message below. I have created an App Id for the app, extension and WatchKit App as well as distribution profiles.
Where am I going wrong?
Thanks
To properly sign a watch app, you need three different App IDs and each App ID needs a provision profile.
Go to Developer Member Center
Add/Edit the three App IDs:
One for your main App bundle, you may need to add the entitlements you need, like App Groups, Keychain Access Group.
One for your watchkit extension bundle, you may need to add the entitlements you need.
One for your watchkit app bundle. No entitlements needed.
Delete the distribution provision profiles for the three App IDs, if they already exists.
Add three new distribution provision profiles for the three App IDs.
Now go back to Xcode, open Preference and go to Accounts.
Choose your Apple ID, click View Details on the bottom right.
Click the refresh button on the bottom left, wait for the list of provision profiles to change.
In Build Settings for all your targets, configure the Code Signing part as below.
Try Archive again.
When you submit your app, XCode will ask you to confirm the provision profile it uses to sign each of your bundles. You need to be sure that the provision profile names match those you configured in Developer Member Center.
I have uploaded one app to itunesconnect with watch app.
This is very simple. You need to create 3 appstore provisioning profiles and the bundle identifier for the extention and watchApp are like
com.abc.app - Phone app
com.abc.app.extention - Extention
com.abc.app.watchapp - watch app
and also sync app group in capabilities tab in all 3 targets.
All are well.
you just needs to create Archive for only Phone App (Main Target). That's It. When user will download your app. And if phone have attached Watch then this will automatically get informed to you for watchapp download.
Judging by the screenshot, it looks like your profiles need to have the missing entitlements (beta-reports-active, keychain-access-groups) added to them.
You will need to create a provisioning profile for the watchkit extension as well as the provision that you have for your app.
If you download the Apple Lister App Code Sample there is a guide to getting started that show you everything that you need to do to setup your app to work properly on a device with Apple Watch.
https://developer.apple.com/library/ios/samplecode/Lister/Introduction/Intro.html
Click on the Download Sample Code button, and in that folder there is a file called iOS and Watch Quick Start.pdf
Using XCode 6.3 solved the problem to me.
I previously used 3 provisionning profiles for watch apps
source : Watchkit Extension - No matching provisioning profiles found