Why is generating them and sticking them in your code bad? Why do you hate it? This is standard practice in many situations, so much that IDEs do it for you sometimes.
Kris On Fri, Feb 15, 2013 at 5:28 AM, tom_mai78101 <[email protected]> wrote: > Re-reading Android Reference, it said the UUID needs to be the same for both > the server-side and the client-side. UUID.randomUUID() and > BluetoothDevice.getUuids() are sure to fail. > > I hate it, but it looks like I need to set up to 7 constant (final) UUIDs > without generating them at compile-time. Will report back once I have some > results. > > -- > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Android Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
