Then don't do that.francof wrote:if I generate it several times, on the same device, the UUID will be always different.

Just write it once on first-run, and then read it in all subsequent runs.
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Then don't do that.francof wrote:if I generate it several times, on the same device, the UUID will be always different.
at present now I've not got duplicated data from devices on which app runs... yes I know, no certainty in this world.jacque wrote:Android build info is not reliable, some manufacturers use the same info on all the devices of the same model. And of the devices I've looked at, many of the identifying entries are listed as simply "unknown" which will match other models too.
...
Ok but if I copy the txt. file in another device? the app will find it and it will start.Simon wrote:Hi franco,
What Richard means is that you should save the UUID to an external file (just a text file) on the device and read that file every time the app is started. Now you will have a unique ID for each device.
Simon
at present now I've not got duplicated data from devices on which app runs
I know you know this, but for the benefit of other readers the UUID Apple prohibits is their own, which several versions back LiveCode used to provide a special function for under a different name. The "UUID" function provided in LiveCode is safe to use on all supported platforms.jacque wrote:Apple forbids the use of the uuid, which is why it has been removed from the build info in LC.
If even that. With Apple's management of app distribution among licensees, developers shouldn't need to spend any time on this at all in iOS. The only risk may be with jailbroken devices, but those are few and so exposed to security risks that it was never a popular thing to do and only less so over time.If you will release to the App Store then Apple will manage ownership. If you are distributing the app yourself then I don't see any other way to manage except to write a file.
Thanks for clarifying that, I should have been more specific. The UUID that Apple forbids is the actual device ID built into the hardware, not the software-generated one that LC creates.I know you know this, but for the benefit of other readers the UUID Apple prohibits is their own, which several versions back LiveCode used to provide a special function for under a different name. The "UUID" function provided in LiveCode is safe to use on all supported platforms.
I believe you, I think a little effort to give a minimum of protection must be done.FourthWorld wrote: ...
Nothing can stop a hacker. Game companies spend millions on software license enforcement, knowing in advance that it will never stop or even significantly reduce piracy, but merely slow down the time-to-crack to at most about 90 days. In the high-stakes game world that's enough to be worth it, but few of us have titles that will produce that kind of money to be worth the effort.
...
true, but not exactly cheap: apple asks credit card number before to say hello".FourthWorld wrote:...
If even that. With Apple's management of app distribution among licensees, developers shouldn't need to spend any time on this at all in iOS.
...
at present in the preopencard I'm going to read this file:jacque wrote:...Android users cannot copy the file to another device unless the phone is rooted, which means the file will be inaccessible to most people.
...
Code: Select all
open file specialFolderPath("DOCUMENTS") & "/att.txt" for read
read from file specialFolderPath("DOCUMENTS") & "/att.txt" until EOF
I don't understand. One of the distinguishing characteristics of iOS is that Apple controls all app distribution on that platform. If not through Apple, how would your distribute your iOS app?francof wrote:true, but not exactly cheap: apple asks credit card number before to say hello".FourthWorld wrote:...
If even that. With Apple's management of app distribution among licensees, developers shouldn't need to spend any time on this at all in iOS.
...
That's right. Files in the documents folder are stored in the app sandbox and other apps can't access it. They can only see files stored in public folders on the drive. You don't need to do anything else.francof wrote: at present in the preopencard I'm going to read this file:you said I cannot copy, or read that file with a text editor, from that folder? or must I do something different?Code: Select all
open file specialFolderPath("DOCUMENTS") & "/att.txt" for read read from file specialFolderPath("DOCUMENTS") & "/att.txt" until EOF
I only meant that, with Apple, to do anything you have to pay:FourthWorld wrote: I don't understand. One of the distinguishing characteristics of iOS is that Apple controls all app distribution on that platform. If not through Apple, how would your distribute your iOS app?
this is good, sure I will make a test.jacque wrote: That's right. Files in the documents folder are stored in the app sandbox and other apps can't access it. They can only see files stored in public folders on the drive. You don't need to do anything else.
It would be easy to test though. Create the file and then try to find it with an Android file browser.
Yes, that's my understanding as well, that the only way distribute any app for iOS requires going through Apple's programs to do so.francof wrote:I only meant that, with Apple, to do anything you have to pay:FourthWorld wrote: I don't understand. One of the distinguishing characteristics of iOS is that Apple controls all app distribution on that platform. If not through Apple, how would your distribute your iOS app?
to test on real device must pay minimun 99$ per year,
if they have the kindness to accept my app on the store must pay,
if the app is sold they take a percentage. etc.
![]()
or am I wrong?
Code: Select all
open file specialFolderPath("DOCUMENTS") & "/code.txt" for write
put field "fldattivazione" into myText
write myText to file specialFolderPath("DOCUMENTS") & "/code.txt"
close file specialFolderPath("DOCUMENTS") & "/code.txt"
ok, thank youjacque wrote:File cleaners only remove temporary and cache files. I don't think they have any access at all to your app's document files.