There can be a few issue that cause the container field to stop working correctly. First I would shutdown and restart FMGo.
Secondly make sure the user has the most update version of FMGo and iOS. Conflicting version is known to cause problems. Security settings and or custom menus can prevent the user from inserting items into a container field. You may have to change available menu commands, if this has been limited in the user login. I usually use the standard Filemaker menu on layouts that require an item to be inserted into a container field on iOS device.
And that is exactly what it turned out to be. After denying the user had made any changes, I found they'd installed the latest update on their iPad without updating FMGo.
The lesson: never trust that the client is telling the truth or understands what has happened.
Thanks for the input schamblee.
This sounds like something we might want to document. Can you provide a little more detail about what your customer was experiencing / seeing with the container fields, what version of the iOS they had and what they updated to (8.2?) and what version of FileMaker Go they had and what version fixed it?
Glad to hear everything worked out.
I seen this reported a couple of time on the FMGo forum. I couldn't find any related post this morning, but I believe TSGAL posted on one of the post. I think the problem started with iOS8, but I'm not 100% sure. TSGAL may have more information, and or may be able to find some older post.
Thanks for the heads up. I'll check with her.