Important Changes for GoZync in iOS7
GoZync4.IOS7 History
Hide minor edits - Show changes to output
Changed lines 3-4 from:
!! What changes in iOS7?
to:
!! Update - All Clear
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks using the latest FileMaker Go and GoZync 4x have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 as described below.
!! What changed in iOS7?
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks using the latest FileMaker Go and GoZync 4x have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 as described below.
!! What changed in iOS7?
Deleted lines 16-19:
!! Updates
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks using GoZync 4 have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 as described below.
Changed lines 20-21 from:
1. If you're using a version of GoZync prior to version 4, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[MigratingFromGoZync3 | upgrade instructions]]. Prior versions will fail under iOS7 and will not work even after FileMaker releases a patch to FileMaker Go.
to:
1. If you're using a version of GoZync prior to version 4, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[MigratingFromGoZync3 | upgrade instructions]]. Prior versions will fail under iOS7 and will not work {-even after FileMaker releases a patch to FileMaker Go-} even now that FileMaker has released a new version of Go.
Changed line 50 from:
-> If you absolutely can't update, please [[http://www.seedcode.com/contact | get in touch]] and we can see if there is a remedy short of updating available, depending on how you're using sync. The most important thing is to make sure your users''' do NOT update to iOS7''' until you have brought your code up to date.
to:
-> If you absolutely can't update to GoZync 4, please [[http://www.seedcode.com/contact | get in touch]] and we can see if there is a remedy short of updating available, depending on how you're using sync. The most important thing is to make sure your users''' do NOT update to iOS7''' until you have brought your code up to date.
Changed lines 22-24 from:
2. Even if you're on version 4, (-ADgasfgaha-)
(-Do not upgrade to iOS7 until we've given you the all-clear on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-) FileMaker has released a patch for Go and all you need to do is this...
(-
to:
2. Even if you're on version 4, {-Do not upgrade to iOS7 until we've given you the all-clear on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-} FileMaker has released a patch for Go and all you need to do is this...
Changed lines 22-24 from:
2. Even if you're on version 4, (-Do not upgrade to iOS7 until we've given you the all-clear on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-) FileMaker has released a patch for Go and all you need to do is this...
to:
2. Even if you're on version 4, (-ADgasfgaha-)
(-Do not upgrade to iOS7 until we've given you the all-clear on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-) FileMaker has released a patch for Go and all you need to do is this...
(-Do not upgrade to iOS7 until we've given you the all-clear on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-) FileMaker has released a patch for Go and all you need to do is this...
Changed line 22 from:
2. Even if you're on version 4, (-'''Do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-) FileMaker has released a patch for Go and all you need to do is this...
to:
2. Even if you're on version 4, (-Do not upgrade to iOS7 until we've given you the all-clear on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-) FileMaker has released a patch for Go and all you need to do is this...
Changed lines 22-25 from:
2. Even if you're on version 4, '''Do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.
3. Now that FileMaker has released a patch for Go, if you're on GoZync 4
3. Now that FileMaker has released a patch for Go, if you're on GoZync 4
to:
2. Even if you're on version 4, (-'''Do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.-) FileMaker has released a patch for Go and all you need to do is this...
Added lines 27-28:
-> 3.3 You should both of these things even if your users aren't moving to iOS7 right away. These changes work in iOS6 and will have you ready for iOS7.
Changed lines 16-17 from:
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks using GoZync 4 have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 a described below.
to:
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks using GoZync 4 have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 as described below.
Changed lines 20-21 from:
1. If you're using a version of GoZync prior to version four, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[MigratingFromGoZync3 | upgrade instructions]]. Prior versions will fail under iOS7 and will not work even after FileMaker releases a patch to FileMaker Go.
to:
1. If you're using a version of GoZync prior to version 4, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[MigratingFromGoZync3 | upgrade instructions]]. Prior versions will fail under iOS7 and will not work even after FileMaker releases a patch to FileMaker Go.
Changed lines 24-28 from:
to:
3. Now that FileMaker has released a patch for Go, if you're on GoZync 4 all you need to do is this...
-> 3.1 Tell all your users to upgrade to the latest version of FMGo in their IOS App Store.
-> 3.2 Log into GoZync License as an administrator and delete all the devices. You may need to do this a few times if your users don’t all upgrade to the latest Go at once. Reason for this is that the new version of FMGO will give everyone new device IDs and the OLD device IDs are already taking up your licensed devices, so you'll need to clear them out.
-> 3.1 Tell all your users to upgrade to the latest version of FMGo in their IOS App Store.
-> 3.2 Log into GoZync License as an administrator and delete all the devices. You may need to do this a few times if your users don’t all upgrade to the latest Go at once. Reason for this is that the new version of FMGO will give everyone new device IDs and the OLD device IDs are already taking up your licensed devices, so you'll need to clear them out.
Added lines 37-38:
-> '''Update'''. Now that FileMaker has released a new version of Go that fixes Persistent ID, the only issue for GoZync users is that they'll get new persistent IDs. This means you'll want to log into GoZync License and delete all the earlier devices to make room for your new ones: you'll find instructions [[ManagingDevices | here]].
Changed line 16 from:
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks %block red%[@ using GoZync 4 have the all-clear to upgrade to iOS7 @]. Folks using previous version of GoZync still need to update to GoZync 4 a described below.
to:
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks using GoZync 4 have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 a described below.
Changed lines 14-16 from:
!! UPDATE
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folksusing GoZync 4 have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 a described below.
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks
to:
!! Updates
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks %block red%[@ using GoZync 4 have the all-clear to upgrade to iOS7 @]. Folks using previous version of GoZync still need to update to GoZync 4 a described below.
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks %block red%[@ using GoZync 4 have the all-clear to upgrade to iOS7 @]. Folks using previous version of GoZync still need to update to GoZync 4 a described below.
Added lines 13-16:
!! UPDATE
Sept 17, 2013 - FileMaker has released an update for FileMaker Go (12.0.8) which fixes the Get ( PersistentID ) for iOS7. (Notes of FileMaker's release are %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074/ | here]].) This means that folks using GoZync 4 have the all-clear to upgrade to iOS7. Folks using previous version of GoZync still need to update to GoZync 4 a described below.
Changed line 30 from:
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't affect the sync, but not ideal.
to:
-> GoZync 4 uses Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all of your users will have the same log entry. Not the end of the world, as it doesn't affect the sync, but not ideal.
Changed line 7 from:
In iOS7 two FileMaker functions will perform differently:
to:
In iOS7 two FileMaker functions will perform differently than they do now:
Changed line 40 from:
-> If you absolutely can't update, please get in touch and we can see if there is a remedy short of updating available, depending on how you're using sync. The most important thing is to make sure your users''' do NOT update to iOS7''' until you have brought your code up to date.
to:
-> If you absolutely can't update, please [[http://www.seedcode.com/contact | get in touch]] and we can see if there is a remedy short of updating available, depending on how you're using sync. The most important thing is to make sure your users''' do NOT update to iOS7''' until you have brought your code up to date.
Changed line 16 from:
1. If you're using a version of GoZync prior to version four, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[version history]]. Prior versions will fail under iOS7 and will not work even after FileMaker releases a patch to FileMaker Go.
to:
1. If you're using a version of GoZync prior to version four, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[MigratingFromGoZync3 | upgrade instructions]]. Prior versions will fail under iOS7 and will not work even after FileMaker releases a patch to FileMaker Go.
Deleted lines 5-6:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of.
Added lines 22-23:
FileMaker is %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074 | aware of the issue]] and while we don't believe they can restore Get ( SystemNicAddress), we expect a patch for FileMaker Go that will get Persistent ID working again.
Changed lines 26-28 from:
The two functions affected (especially Get ( PersistentID )) are used to uniquely identify iOS devices. Many developers use this in their licensing routines, for example. Some developers who roll their own sync or don't use [[UUIDs]] may even use these functions as part of syncing data itself. All these things will likely break in iOS7 until FileMaker releases a patch.
FileMaker is %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074 | aware of the issue]] and while we don't believe they can restore Get ( SystemNicAddress), we expect a patch for FileMaker Go that will get Persistent ID working again.
FileMaker is %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074 | aware of the issue]] and while we don't believe they can restore Get ( SystemNicAddress), we expect a patch for FileMaker Go that will get Persistent ID working again.
to:
The two functions affected (especially Get ( PersistentID )) are used to uniquely identify iOS devices. Some developers who roll their own sync or don't use [[UUIDs]] may even use these functions as part of syncing data itself. All these things will likely break in iOS7 until FileMaker releases a patch.
Changed line 11 from:
-> Get ( SystemNICAddress ) will return the same value for all devices.
to:
-> Get ( SystemNICAddress ) will fail.
Changed line 16 from:
!! Is GoZync Affected & What should I do now?
to:
!! Is GoZync Affected: what should I do now?
Changed line 16 from:
!! What should I do now?
to:
!! Is GoZync Affected & What should I do now?
Added lines 5-6:
%center% %rfloat width=120px% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
Deleted lines 7-8:
%center% %rfloat width=120px% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
Changed line 7 from:
%center% %float width=120px% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
to:
%center% %rfloat width=120px% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
Changed line 7 from:
%center% %width=100ox% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
to:
%center% %float width=120px% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
Changed line 7 from:
%center% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
to:
%center% %width=100ox% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
Changed line 32 from:
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't affect the sync, but not ideal. And if two users are syncing at the same time, one may get an error that the log can't be written to because another user is writing to it.
to:
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't affect the sync, but not ideal.
Changed line 34 from:
-> GoZync 4 also uses Persistent ID for licensing, so if you upgrade to iOS7, all your devices will get a new (though the same) ID. This means that you'll likely be told you're exceeding your licenses when you next connect: simply delete all the earlier devices to make room for your new one. If you haven't managed/ deleted devices in GoZync before, you'll find instructions here: [[ManagingDevices]].
to:
-> GoZync 4 also uses Persistent ID for licensing, so if you upgrade to iOS7, all your devices will get a new ID. This means that you'll likely be told you're exceeding your licenses when you next connect: simply delete all the earlier devices to make room for your new ones. If you haven't managed/ deleted devices in GoZync before, you'll find instructions here: [[ManagingDevices]].
Changed line 32 from:
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't affect the sync, but not ideal.
to:
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't affect the sync, but not ideal. And if two users are syncing at the same time, one may get an error that the log can't be written to because another user is writing to it.
Changed lines 18-20 from:
1. If you're using a version of GoZync prior to version four, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[version history]]. Prior versions will fail under iOS7.
2. If at all possible, '''do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.
2. If at all possible, '''do
to:
1. If you're using a version of GoZync prior to version four, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[version history]]. Prior versions will fail under iOS7 and will not work even after FileMaker releases a patch to FileMaker Go.
2. Even if you're on version 4, '''Do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.
2. Even if you're on version 4, '''Do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.
Changed line 26 from:
FileMaker is %newwin% [[aware of the issue]] and while we don't believe they can restore Get ( SystemNicAddress), we expect a patch for FileMaker Go that will get Persistent ID working again.
to:
FileMaker is %newwin% [[http://help.filemaker.com/app/answers/detail/a_id/12074 | aware of the issue]] and while we don't believe they can restore Get ( SystemNicAddress), we expect a patch for FileMaker Go that will get Persistent ID working again.
Added lines 25-26:
FileMaker is %newwin% [[aware of the issue]] and while we don't believe they can restore Get ( SystemNicAddress), we expect a patch for FileMaker Go that will get Persistent ID working again.
Changed lines 18-20 from:
1. If you're using a version of GoZync prior to version 4, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[version history]].
2. If at all possible, '''do not upgrade tountil we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly.
2. If at all possible, '''do not upgrade to
to:
1. If you're using a version of GoZync prior to version four, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[version history]]. Prior versions will fail under iOS7.
2. If at all possible, '''do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.
2. If at all possible, '''do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly. Read on to learn what exactly happens to GoZync 4 under iOS7, but the short answer is that it would be best for you to postpone upgrading until FileMaker releases a patch for FileMaker Go.
Changed lines 24-25 from:
The two functions effected (especially Get ( PersistentID )) are used to uniquely identify iOS devices. Many developers use this in their licensing routines, for example. Some developers who roll their own sync or don't use [[UUIDs]] may even use these functions as part of syncing data itself. All these things will likely break in iOS7 until FileMaker releases a patch.
to:
The two functions affected (especially Get ( PersistentID )) are used to uniquely identify iOS devices. Many developers use this in their licensing routines, for example. Some developers who roll their own sync or don't use [[UUIDs]] may even use these functions as part of syncing data itself. All these things will likely break in iOS7 until FileMaker releases a patch.
Changed line 30 from:
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't effect the sync, but not ideal.
to:
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't affect the sync, but not ideal.
Changed line 18 from:
1. If you're using a version of GoZync prior to version 4, please update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. Update instructions are here: [[version history]].
to:
1. If you're using a version of GoZync prior to version 4, you '''must update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. This is a free update and instructions are here: [[version history]].
Changed line 20 from:
2. If at all possible, '''do not upgrade to iOS7 until we've given you the all clear''' here. We're hoping that FileMaker addresses this issue quickly.
to:
2. If at all possible, '''do not upgrade to iOS7 until we've given you the all-clear''' on this page. We're hoping that FileMaker addresses this issue quickly.
Changed lines 18-22 from:
1. If you're using a version of GoZync prior to version 4, please update to version 4 as soon as possible. Version 4 does NOT use these functions for mission critical operations.
2. If at all possible, do not upgrade to iOS7 until weve given you the all clear here. We're hoping that FileMaker addresses this issue quickly.
!! Background
2. If at all possible, do not upgrade to iOS7 until we
!! Background
to:
1. If you're using a version of GoZync prior to version 4, '''please update to version 4 of GoZync''' as soon as possible. Version 4 does NOT use these functions for mission critical operations. Update instructions are here: [[version history]].
2. If at all possible, '''do not upgrade to iOS7 until we've given you the all clear''' here. We're hoping that FileMaker addresses this issue quickly.
!! Background
The two functions effected (especially Get ( PersistentID )) are used to uniquely identify iOS devices. Many developers use this in their licensing routines, for example. Some developers who roll their own sync or don't use [[UUIDs]] may even use these functions as part of syncing data itself. All these things will likely break in iOS7 until FileMaker releases a patch.
'''GoZync Version 4 and higher.'''
-> GoZync 4 does NOT use these functions for syncing itself.
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't effect the sync, but not ideal.
-> GoZync 4 also uses Persistent ID for licensing, so if you upgrade to iOS7, all your devices will get a new (though the same) ID. This means that you'll likely be told you're exceeding your licenses when you next connect: simply delete all the earlier devices to make room for your new one. If you haven't managed/ deleted devices in GoZync before, you'll find instructions here: [[ManagingDevices]].
'''Earlier versions of GoZync'''
-> Earlier versions use Get ( SystemNICAddress ) as part of Field Level Merge and elsewhere. These versions will not sync correctly under iOS7 and should NOT be used.
-> The best option is to [[version history | update to GoZync 4]] (that's a free update for GoZync 3 users).
-> If you absolutely can't update, please get in touch and we can see if there is a remedy short of updating available, depending on how you're using sync. The most important thing is to make sure your users''' do NOT update to iOS7''' until you have brought your code up to date.
2. If at all possible, '''do not upgrade to iOS7 until we've given you the all clear''' here. We're hoping that FileMaker addresses this issue quickly.
!! Background
The two functions effected (especially Get ( PersistentID )) are used to uniquely identify iOS devices. Many developers use this in their licensing routines, for example. Some developers who roll their own sync or don't use [[UUIDs]] may even use these functions as part of syncing data itself. All these things will likely break in iOS7 until FileMaker releases a patch.
'''GoZync Version 4 and higher.'''
-> GoZync 4 does NOT use these functions for syncing itself.
-> GoZync 4 does use Get ( PersistentID ) for logging, so if you do upgrade to iOS7, all your users will have the same log entry. Not the end of the world, as it doesn't effect the sync, but not ideal.
-> GoZync 4 also uses Persistent ID for licensing, so if you upgrade to iOS7, all your devices will get a new (though the same) ID. This means that you'll likely be told you're exceeding your licenses when you next connect: simply delete all the earlier devices to make room for your new one. If you haven't managed/ deleted devices in GoZync before, you'll find instructions here: [[ManagingDevices]].
'''Earlier versions of GoZync'''
-> Earlier versions use Get ( SystemNICAddress ) as part of Field Level Merge and elsewhere. These versions will not sync correctly under iOS7 and should NOT be used.
-> The best option is to [[version history | update to GoZync 4]] (that's a free update for GoZync 3 users).
-> If you absolutely can't update, please get in touch and we can see if there is a remedy short of updating available, depending on how you're using sync. The most important thing is to make sure your users''' do NOT update to iOS7''' until you have brought your code up to date.
Changed lines 11-17 from:
-> Get (
!! What do I need to do?
First, do not upgrade to iOS7 until we've released a
cbafb
!! What do I need to do?
First, do not upgrade to iOS7 until we've released a
cbafb
to:
-> Get ( SystemNICAddress ) will return the same value for all devices.
-> Get ( PersistentID ) will return the same value for all devices.
This means that if you're using these functions for mission critical aspects of your solution you'll need to retool or postpone upgrading to iOS7 until there is a fix from FileMaker.
!! What should I do now?
1. If you're using a version of GoZync prior to version 4, please update to version 4 as soon as possible. Version 4 does NOT use these functions for mission critical operations.
2. If at all possible, do not upgrade to iOS7 until we've given you the all clear here. We're hoping that FileMaker addresses this issue quickly.
-> Get ( PersistentID ) will return the same value for all devices.
This means that if you're using these functions for mission critical aspects of your solution you'll need to retool or postpone upgrading to iOS7 until there is a fix from FileMaker.
!! What should I do now?
1. If you're using a version of GoZync prior to version 4, please update to version 4 as soon as possible. Version 4 does NOT use these functions for mission critical operations.
2. If at all possible, do not upgrade to iOS7 until we've given you the all clear here. We're hoping that FileMaker addresses this issue quickly.
Changed lines 5-7 from:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of. %float width=120px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
to:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of.
%center% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
%center% [[http://www.apple.com/ios/ | http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg]]
Changed line 5 from:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of. %float% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
to:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of. %float width=120px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
Changed lines 5-7 from:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of.
%float% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
%float% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
to:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of. %float% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
Changed line 7 from:
%float width=140px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
to:
%float% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
Changed lines 5-8 from:
to:
The new iOS from Apple will introduce at least one big change for FileMaker Go that developers should be aware of.
%float width=140px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
In iOS7 two FileMaker functions will perform differently:
-> Get (
%float width=140px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
In iOS7 two FileMaker functions will perform differently:
-> Get (
Changed lines 17-19 from:
to:
cbafb
!! Background
!! Background
Changed line 5 from:
%float width=90px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
to:
%floatright width=120px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
Changed line 5 from:
%float% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
to:
%float width=90px% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
Added lines 4-5:
%float% http://www.seedcode.com/rootimages/stikipad/gozync/i0s7.jpg
Changed line 1 from:
(:title Important Changes in iOS7:)
to:
(:title Important Changes for GoZync in iOS7:)
Added lines 1-11:
(:title Important Changes in iOS7:)
!! What changes in iOS7?
fasgra
!! What do I need to do?
First, do not upgrade to iOS7 until we've released a
cbafb
!! What changes in iOS7?
fasgra
!! What do I need to do?
First, do not upgrade to iOS7 until we've released a
cbafb
