Wouldn't it be easier to just generate a random on first start, store it
somewhere in application persistance, and do whatever you would be doing
with that unreachable UDID/IMEI/Ad ID ?

How do agents "register" their customers? Can't customers just key in their
agent "keycode/pin/name/email/phone number" (or even select it from their
local contacts) on first run, and just forget about the unique ID?

Also, maybe this helps:
https://mateuszmackowiak.wordpress.com/2012/02/23/adobe-air-native-extension-syste/

that they can give to their clients


Describe how this is done :-? Agents personally install it on their
customer's phones?

On Tue, Dec 19, 2017 at 12:18 AM, bilbosax <waspenc...@comcast.net> wrote:

> I don't want to overwhelm anyone with the details of what I am trying to
> do,
> but in a nutshell, I am trying to develop a mobile AIR app for real estate
> agents that is customizeable that they can give to their clients and, and
> when the client installs it, it will look like the real estate agent wrote
> it themselves and will have their branding in the app.
>
> To do this, I need to save a unique identifier from any Android or iOS
> device that installs the app.  Apparently, this is inconsistent approach
> and
> not supported across all devices, so I can't do something simple like store
> a MAC address or a UDID because not all devices will allow access to these
> identifiers, so I would get inconsistent results.
>
> The only consistent identifiers that I have been able to narrow down are
> Advertising ID's.  These are provided by both iOS and Android devices and
> there are ANE's available that will give you access to these identifiers.
> What I am concerned with is this - I am not using them to provide Ads to my
> users.  I just need to know who a user is and associate them with a real
> estate agent consistently.
>
> Does anyone know if Apple or Google will throw up a fuss if you try to
> submit an app to the app store that uses an Advertising ID, but is not
> using
> it to serve up ads???
>
> Thanks for any thoughts!
>
>
>
> --
> Sent from: http://apache-flex-users.2333346.n4.nabble.com/
>

Reply via email to