Yesterday I tried to submit the application again, Apple accepted it right away. Thanks for the fix!

8,2 now is latest

Ok, I will try tomorrow with that new version.

Hi Stan,

sorry for the delay,
V4RB mac archive with this fix is here
http://valentina-db.com/download/prev_releases/8.1.1/mac_32

Please try it and let us know.

Hello Stan,

Thanks for the report, we've found the problem, the fix will be available in the next build, we'll let you know once it will be uploaded.

Yes, I get this error as soon as I launch the application:

Sandbox: iCash SE(5097) deny file-write-data /Users/maxprog/Dropbox/Developments/_projects/icash/dev/Builds - iCash v7.6.4 64-bit.xojo_binary_project/OS X 64 bit/iCash http://SE.app/Contents/vcomponents_x64/vresources/en/kernel_errors.xml
Violation: deny file-write-data /Users/maxprog/Dropbox/Developments/_projects/icash/dev/Builds - iCash v7.6.4 64-bit.xojo_binary_project/OS X 64 bit/iCash http://SE.app/Contents/vcomponents_x64/vresources/en/kernel_errors.xml
MetaData: {"build":"Mac OS X 10.13.3 (17D102)","action":"deny","target":["Users","maxprog","Dropbox","Developments","_projects","icash","dev","Builds - iCash v7.6.4 64-bit.xojo_binary_project","OS X 64 bit","iCash SE.app","Contents","vcomponents_x64","vresources","en","kernel_errors.xml"],"hardware":"Mac","platform_binary":"no","profile":"unknown","process":"iCash SE","op":"file-write-data"}

Process: iCash SE [5097]
Path: /Users/maxprog/Dropbox/Developments/_projects/icash/dev/Builds - iCash v7.6.4 64-bit.xojo_binary_project/OS X 64 bit/iCash http://SE.app/Contents/MacOS/iCash SE
Load Address: 0x10a572000
Identifier: com.maxprog.app.icash
Version: 7.6.4 (7.6.4)
Code Type: x86_64 (Native)
Parent Process: launchd [1]
Responsible: /Users/maxprog/Dropbox/Developments/_projects/icash/dev/Builds - iCash v7.6.4 64-bit.xojo_binary_project/OS X 64 bit/iCash http://SE.app/Contents/MacOS/iCash SE [5097]
User ID: 501

Date/Time: 2018-03-29 11:33:08.385 GMT+2
OS Version: Mac OS X 10.13.3 (17D102)
Report Version: 8

Thread 0 (id: 46649842):
0 libsystem_kernel.dylib 0x00007fff6bfffb3a __open + 10
1 CarbonCore 0x00007fff45352647 FSMount::_openfork(char const*, unsigned char, unsigned int, unsigned short, _filesec*, int*, int*, FSOpenForkInfo*) + 643
2 CarbonCore 0x00007fff45351f3b FSMount:penforkcoreDefault(unsigned int, unsigned int, unsigned int, char const*, char const*, unsigned int, unsigned char, unsigned char, FSOpenForkInfo*, unsigned short, _filesec*, unsigned int, int*, unsigned int*, unsigned int*) + 939
3 CarbonCore 0x00007fff453515e2 PBOpenForkSync + 506
4 CarbonCore 0x00007fff453513d5 FSOpenFork + 47
5 libvshared_fat_release_x64.dylib 0x00000001103218ba fbl::File_Mac:oOpen() + 234
6 libvshared_fat_release_x64.dylib 0x0000000110320f36 fbl::File::Open() + 36
7 libvkernel_fat_release_x64.dylib 0x0000000111a762c4 fbl::LoadErrorResourceFile(fbl::String const&, fbl::ErrorEntry* (*)(unsigned int), unsigned int) + 213
8 libvkernel_fat_release_x64.dylib 0x0000000111a7601a fbl::LoadErrorResource(unsigned short const*, unsigned int) + 137
9 libvkernel_fat_release_x64.dylib 0x0000000111b5ef86 fbl::ValentinaInit_imp(unsigned int, char const*, char const*, char const*) + 66
10 libvkernel_fat_release_x64.dylib 0x0000000111b5eed4 fbl::ValentinaInit(unsigned int, char const*, char const*, char const*) + 20
11 v4rb_cocoa_64.dylib 0x0000000110234d89 Valentina_Init(int, REALstringStruct*, REALstringStruct*, REALstringStruct*) + 35
12 iCash SE 0x000000010a735ce5 Valentina.Init%%i8sss + 85

1.Run the Console.app
2. Run the application.
Is there any error in the log? If any error - they even show the call stack on double-click.

I can already test my Sandboxed app (my way), what do you want me to do?

Your application is signed for distribution.
If you sign for development - with development certificate and mac developer identity, install development profile - you will be able to test signed application on your system.

These files are opened read-only in code:
pFile->put_Location( resPath );
pFile->put_IsReadOnly( true );
pFile->Open();

Apple is clear, do not open the file in read/write mode. Maybe it is a new requirement. You know Apple, they add new requirements regularly. You will find my package structure attached. You will see everything is correct. I already distribute this app in my web site.

And yes, my app is properly signed, note that I have submitted 2 applications successfully to the app store this week. Everything works fine for me here.

Stan

That's strange, we don't have such issue posting to the App Store.

Please attach your application structure to be sure that everything was copied.

Did you try to run the application signed with your development certificate?
Thus you will see the complete error from the sandbox in the Console.app.

i think it has to do with those location not being allowed. make use of container for you app and use those files from there.

Apple has rejected the my app again with the very same error, what can I do to fix that problem?

Stan

I prepared the application with install_vcomponents_v4rb_v7
I have submitted the app again with those two files as read-only. Let see the result...

Stan

So they want a read-only opening.

Maybe try to set these files to have a read-only flag.
This should force opening them in read-only mode.

Hello Stanley,

Did you prepare the application using the install_vcomponents_v4rb_v7 script?