On a device (works correctly on simulator) running iOS version 7.1, the app crashes with an assert failure after signing and completing assignment.
To Reproduce:
Launch iOS app and login
Click "Active" button for top current assignment and select complete.
Click "Add Signature" button and add and save your signature.
Click Complete button and answer "yes" to alert dialog.
Expected result: assignment is completed and app continues to run.
Actual result: App crashes with:
Assertion failed: (tb.x == CGRectGetMinX(tile_bounds)), function ripc_GetPattern, file RIP/RIPColor.c, line 803.
Also, when loading the AssignmentsController, there are ~420 lines similar to the following:
FieldServiceiOS[2181] : CGContextSaveGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
These do not seem to cause a crash, but why look like serious warnings. It even says "Serious error" . :-)
@jgold6 Can you confirm that this issue is fixed at current version (from master).
I am sure that this issue was before unified api. Now app works fine for me
On a device (works correctly on simulator) running iOS version 7.1, the app crashes with an assert failure after signing and completing assignment.
To Reproduce:
Expected result: assignment is completed and app continues to run. Actual result: App crashes with: Assertion failed: (tb.x == CGRectGetMinX(tile_bounds)), function ripc_GetPattern, file RIP/RIPColor.c, line 803.
Also, when loading the AssignmentsController, there are ~420 lines similar to the following: FieldServiceiOS[2181]: CGContextSaveGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
These do not seem to cause a crash, but why look like serious warnings. It even says "Serious error" . :-)