Is there any way to start developing and working with the framework without getting access from Google ?
now also they didnt give me access to
CtDM
C2DM is in a slow rolling beta. I imagine they got thousands of applicants, and they are only going to take on people at a pace that they can support.
is there any way to start developing
and working with the framework without
getting access from Google?
No. You are welcome to write your own push framework, but C2DM requires Google servers, and for the beta, your C2DM-enabled Google account needs to be on a whitelist.
check this:
https://stackoverflow.com/a/7888059/371749
devices need a google account to use this service! :=)
good luck!
Related
My app uses firebase phone auth to allow users to register, the issue is that I don't receive any verification code. but when I use a VPN app and try, it works!!
am sure that there is no issue in the code, since it works when I use a VPN. am wondering is it cause of my current location (I am based in Sudan)? although Sudan is listed in among the countries where the service is offered too in the documentation.
I think it could be that google services doesn't work here? but play store, other features etc. work like a charm. I know Sudan is under US sanction, so are other countries - does that mean this feature wont work at all?
If anyone knows whats going on let me know please!
Thank you
It seems that there is no way around it, due to the sanctions exposed in Sudan firebase or in fact all google services will not work unless you use a VPN.
For anyone else who runs into something like this, i did use a work around using this service.
Hope this helps!
I'm trying to implement an MDM client app for Android, known in the Android For Work world as a Device Policy Controller or DPC. Google's documentation for building a DPC is here.
The documented process begins with downloading the DPC Support Library. Unfortunately, the download link they provide (to the "EMM Community's Technical Integration" section) doesn't work: you're prompted to log in with a Google account, but after doing so I see this:
We’re sorry...
...but it looks like you don’t have access to this place or content. If you think you should have access to this space, try logging out and back in again using your account menu accessible by clicking your avatar in the top right corner of this page. If this issue persists, please notify your Support Representative and we will troubleshoot further.
Others have had the same problem: there's an issue ticket raised here which is only 2 months old, has no answer but for some reason has been marked Assumed Answered and then ignored.
The steps documented here make it very clear that the DPC Support Library is a required part of the process, and don't describe any alternatives to using it.
So, how do I get hold of the DPC Support Library? Can it be obtained anywhere else? Or failing that, how do I find out what it does so I can reproduce those steps manually in my own code?
Some steps I've already tried:
I have successfully registered for the EMM Community and have access to the EMM API. (i.e. I get a valid response now from Enterprises.generateSignupUrl, and no longer the dreaded "The caller is not registered as an MDM".) That in itself was a long and frustratingly opaque process.
I have built and run the googlesamples/android-testdpc app and looked through the source code. Unfortunately this is a client-only demo: it doesn't communicate with an EMM server and doesn't use the DPC Support Library. Specifically, it doesn't obtain an authorisation token in order to provision a work profile on the device, as documented here.
I have played with the public EMM demo system and its DPC app. That seems to be doing things properly, but as it's closed-source I can't look at the code for either client or server.
Well I now have access, so in that sense I have an answer, but I don't know how useful it'll be to others.
A Google representative replied to my forum post here and granted my organisation access to the EMM Community. Once that was enabled, the steps were as follows:
Create a new Google account using my work e-mail address
Sign into the Cloud Connect portal with that account
Click on EMM Community
Scroll down to the Featured Technical Guidance section and look for the DPC Support Library download link
An alternative to build your own Device Policy Controller app is to use the Android Management API and therefore not have to use the DPC Support Library. This API doesn't have all the features you can get by building your own Device Policy Controller app, but is significantly simpler to implement.
i am Totally freshers in integrate google assistance into android app.i have task to integrate google assistance into android application.i am researching from last 3 days.i have some question need to clear first.
Here they are.
I have application that handle one machine via Bluetooth.in application there are four buttons that perform different action.Now here i have to do.
suppose i speak "Ok google,let me talk to [some invocation name]"
then it will redirect to my application and perform some action.
How can i do this ?
Help me for this.
Once Your Assistant app is approved by Actions on Google, then your api.ai agent will be available to anyone through 'Ok google'. So, when you speak "Ok google, let me talk to [some invocation name]" then it will open up your agent. So you have to implement your api.ai agent for your machine controlling thing.
I think you can use webhook option in the api.ai to sent control commands to a 3rd party and you have to use that 3rd party to control your machine. This 3rd party can be your android application and you can use push notification or something(use any communication method with android application) to receive commands from api.api agent and do the controlling of your machine.
And also I don't think google assistant will open up your mobile app when you say "Ok google, let me talk to [some invocation name]". Google assistant only open ups the agents that we registered in 'Actions on Google'.
You can try with 'Google Assistant SDK' and try to implement an android app. But still there is no android documentations or samples for that.
Also I think using Google Assistant gRPC API, you can develop some standalone google assistant solution.
https://api.ai/
you will have to read the documenation of googles new converstion api. There you will find answers for your questions.
This is a very fresh topic since google just released the api a few days ago.
Developing an android app that needs tasks from outlook.office365.com, where the client's work account is connected with AD, I used ADAL library for authentication and don't find API to access the Tasks. Is there any way to get this done?.Kindly update me.
Finally, I have found out a way to access the "Tasks" from outlook.office365.com, Please make sure you read the guide here:
https://docs.google.com/document/d/1iqY_tdyJFbVZ2UR0_rGznSvbamDTdm6gNoltfQZghrQ/edit?usp=sharing
It is working, but I had to get the trial license from the developers, still I'm working on the same by using ews-java-api, once if I find it working, I'll update my answer
Sorry, the API doesn't support interacting with Outlook tasks. You can find all of the Office 365 API documentation on MSDN.
When should we use Google Play's service Application Licensing?
Is this a new mechanism against cracked apps on Android?
When should I recommend my clients to use this service? I have read the tutorial, but it did not answer to my queries.
I first thought that this is a mechanism for multimedia-selling apps only, but now I see I was wrong.
If anyone used this service, please tell me why you used it.
When should we use Google Play's service Application Licensing?
When you have an application that you fear will be pirated, and sold/modified without your permission.
Is this a new mechanism against cracked apps on Android?
This system itself has been cracked. Application Licensing uses the LVL library. AntiLVL can crack it.
It's best to implement this in addition to your own authentication methods(Cntrl+F for "Guidelines for custom policies".