Plugin will not stay enabled in FMS 22.0.1.66

[mw777eds]

Describe the bug
Enabling the current version of the plugin in the admin console does not "stick" attempting to restart server or even navigating away and back shows it as disabled.

To Reproduce
Install server on macOS 15.5
Enable plugins on server
Install latest version
Enable and restart

Expected behavior
The toggle to stay on

Additional context

• If you're using any of the curl functions ( HTTP, SMTP, FTP, etc ) include the output of the BE_CurlTrace function, after the function call.
• Or the output of the BE_DebugInformation for newer plugin versions - if it includes the Trace then a separate trace isn't required.

If the trace/debug is large, you may need to save that to a text file and attach separately.

[jsrcomp]

You're lucky it was that and not what I had happen, I knew there was a reason I was on an older version of the plugin and I found out today when I upgraded server 2024 to 2025. A few nights ago I had updated the plugin version on the server and I had forgotten about that so I was stumped for a while as to why fmsased kept restarting. I saw a post about it crashing and a suggestion was to disable plugins, then I remembered why I was running an old version of the plugin...

[nickorr]

What version of the plugin are you using? Does it create a crash log?

[mw777eds]

I am using the most recent macOS plugin and I haven’t seen a crash log it just doesn’t stay enabled.

…

On Jul 30, 2025, at 8:55 PM, Nicholas Orr ***@***.***> wrote: nickorr left a comment (GoyaPtyLtd/BaseElements-Plugin#250) <#250 (comment)> What version of the plugin are you using? Does it create a crash log? — Reply to this email directly, view it on GitHub <#250 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4SNDRINBDY6XHKZXNSYGD3LFZRDAVCNFSM6AAAAACCV3KAVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMZYGMYTOMZTGY>. You are receiving this because you authored the thread.

[jsrcomp]

@nickorr, I was using v5.0. I happened to still have a copy of 4.2.6 that I reinstalled. Where would l look for a log file?
Is there a debug mode I can enable or anything for the plugin?
Happy to help in anyway that I can.

[nickorr]

I am using the most recent macOS plugin and I haven’t seen a crash log it just doesn’t stay enabled.
…

Just giving "most recent" is not helpful, there is latest public, recent beta, even different releases for different platforms. If you're needing support please document the BE_Version_AutoUpdate result.

[nickorr]

@nickorr, I was using v5.0. I happened to still have a copy of 4.2.6 that I reinstalled. Where would l look for a log file? Is there a debug mode I can enable or anything for the plugin? Happy to help in anyway that I can.

On a Mac, there's an app in Utilities called Console. It will have a bunch of logs, but also will have crash logs, if they appear. So you can usually find something that looks like a crash log file for FMSE. Attach those, or if you're concerned about private info, email them to me nick@goya.com.au

What plugin version(s) are you trying with, and what was the result?

[mw777eds]

@nickorr 05000002 version

fmsased-2025-08-05-160218.ips.zip

[nickorr]

@nickorr 05000002 version

fmsased-2025-08-05-160218.ips.zip

Thanks, this is helpful.

For those following, this is a Mac .ips file, which you can open in the Console app. When you do that, you can see at the top some lines :

Crashed Thread:        15

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   fmsased [39543]

So, yes thread 15 crashed, and the process is fmsased which is the FMS server scripting process. Scroll down to thread 15 and you get :

Thread 15 Crashed:
0   libsystem_kernel.dylib        	       0x197b31388 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x197b6a88c pthread_kill + 296
2   libsystem_c.dylib             	       0x197a73c60 abort + 124
3   libc++abi.dylib               	       0x197b2039c abort_message + 132
4   libc++abi.dylib               	       0x197b0ed0c demangling_terminate_handler() + 344
5   libobjc.A.dylib               	       0x197794dd4 _objc_terminate() + 156
6   libc++abi.dylib               	       0x197b1f6b0 std::__terminate(void (*)()) + 16
7   libc++abi.dylib               	       0x197b22c48 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 88
8   libc++abi.dylib               	       0x197b22bf0 __cxa_throw + 92
9   libobjc.A.dylib               	       0x19778acf8 objc_exception_throw + 448
10  Foundation                    	       0x1992d5a78 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 288
11  UserNotifications             	       0x1a5b98e58 __53+[UNUserNotificationCenter currentNotificationCenter]_block_invoke.cold.2 + 116
12  UserNotifications             	       0x1a5b674d8 __53+[UNUserNotificationCenter currentNotificationCenter]_block_invoke + 472
13  libdispatch.dylib             	       0x1979cc85c _dispatch_client_callout + 16
14  libdispatch.dylib             	       0x1979b5a28 _dispatch_once_callout + 32
15  UserNotifications             	       0x1a5b672fc +[UNUserNotificationCenter currentNotificationCenter] + 156
16  BaseElements                  	       0x14c00e25c InitialiseForPlatform() + 132
17  BaseElements                  	       0x14c0be934 LoadPlugin(FMX_ExternCallStruct*) + 120
18  BaseElements                  	       0x14c0be7b0 FMExternCallProc + 208
19  DBEngine                      	       0x10b438f58 Draco::DBPlugIn::MakeCall(unsigned char, char, unsigned char, unsigned long, unsigned long, unsigned long) const + 256
20  DBEngine                      	       0x10b438360 Draco::DBPlugIn::SetStatus(Draco::DBPlugIn::State, Draco::DBPlugIn::AddPlugInFlags) + 252
21  FMS                           	       0x10284ab08 FMS::ServerPluginItem::LoadPlugin() + 272
22  FMS                           	       0x10284cc8c FMS::ServerPluginsHelper::UpdatePlugins(unsigned int&) + 144
23  fmsased                       	       0x1000a0258 FMScriptMgr::GetAndUpdatePlugins(bool) + 104
24  fmsased                       	       0x1000a16cc FMScriptMgr::EnablePluginRequest(FMS::EventHelper&, bool) + 240
25  FMS                           	       0x1026fa994 FMS::ComponentBaseThread::Main() + 196
26  fmsased                       	       0x10009fe6c FMScriptMgr::Main() + 336
27  Support                       	       0x10d2ba734 Draco::Thread::RunThread() + 76
28  Support                       	       0x10d2b96a4 Draco::Thread::ThreadUnixProc(void*) + 156
29  libsystem_pthread.dylib       	       0x197b6ac0c _pthread_start + 136
30  libsystem_pthread.dylib       	       0x197b65b80 thread_start + 8

The top is higher level, and the bottom is lower level, so work from the bottom up.

At line 27, we see it's Draco, which is the name of the FileMaker engine.
Line 24 is fmsased running EnablePluginRequest which I presume is FMS trying to load a plugin.
Line 21 is LoadPlugin from FMS.

Line 18 is the first call to BE itself.
17 is LoadPlugin but inside BE, which is a function in BE.
16 is InitialiseForPlatform which amongst other things does setup for notifications ...

which after that you can see OS related functions being called, all around notifications.

So this is super helpful, and likely means we need to disable notifications on FMS on Mac - because they shouldn't be active on the server anyway.

Thanks, this is a bug, we'll get onto it.

Cheers,
Nick

[nickorr]

There is a test build of 5.1.0 for Mac you can get here :

https://www.dropbox.com/scl/fi/gsiybbelyt7lzzdlsztoj/BaseElements.fmplugin.dmg?rlkey=nh3cueigo2wua90eyn8iu17hl&dl=1

I think this solves the notifications issue, but I have at least one other issue with this release : #252 I don't yet know the cause of that one, if it's text or xml related, so there may be other effects.

If it loads on your FMS on Mac, then you can run the BE Tests file :

https://github.com/GoyaPtyLtd/BaseElements-Plugin/blob/master/Project/Extras/BaseElements%20Plugin%20Tests.fmp12

Hosted on server, it will report all the things that FMS can do and skip any it can't, to confirm any other issues. If there are issues, send me exact details of FMS and OS versions and a copy of the file : nick@goya.com.au

Cheers,
Nick

[jsrcomp]

Thank you very much for the info! I have often looked at the crash reports but didn’t know how to make sense of it...

…

On Aug 5, 2025, at 19:06, Nicholas Orr ***@***.***> wrote: nickorr left a comment (GoyaPtyLtd/BaseElements-Plugin#250) @nickorr 05000002 version fmsased-2025-08-05-160218.ips.zip Thanks, this is helpful. For those following, this is a Mac .ips file, which you can open in the Console app. When you do that, you can see at the top some lines : Crashed Thread: 15 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: fmsased [39543] So, yes thread 15 crashed, and the process is fmsased which is the FMS server scripting process. Scroll down to thread 15 and you get : Thread 15 Crashed: 0 libsystem_kernel.dylib 0x197b31388 __pthread_kill + 8 1 libsystem_pthread.dylib 0x197b6a88c pthread_kill + 296 2 libsystem_c.dylib 0x197a73c60 abort + 124 3 libc++abi.dylib 0x197b2039c abort_message + 132 4 libc++abi.dylib 0x197b0ed0c demangling_terminate_handler() + 344 5 libobjc.A.dylib 0x197794dd4 _objc_terminate() + 156 6 libc++abi.dylib 0x197b1f6b0 std::__terminate(void (*)()) + 16 7 libc++abi.dylib 0x197b22c48 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 88 8 libc++abi.dylib 0x197b22bf0 __cxa_throw + 92 9 libobjc.A.dylib 0x19778acf8 objc_exception_throw + 448 10 Foundation 0x1992d5a78 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 288 11 UserNotifications 0x1a5b98e58 __53+[UNUserNotificationCenter currentNotificationCenter]_block_invoke.cold.2 + 116 12 UserNotifications 0x1a5b674d8 __53+[UNUserNotificationCenter currentNotificationCenter]_block_invoke + 472 13 libdispatch.dylib 0x1979cc85c _dispatch_client_callout + 16 14 libdispatch.dylib 0x1979b5a28 _dispatch_once_callout + 32 15 UserNotifications 0x1a5b672fc +[UNUserNotificationCenter currentNotificationCenter] + 156 16 BaseElements 0x14c00e25c InitialiseForPlatform() + 132 17 BaseElements 0x14c0be934 LoadPlugin(FMX_ExternCallStruct*) + 120 18 BaseElements 0x14c0be7b0 FMExternCallProc + 208 19 DBEngine 0x10b438f58 Draco::DBPlugIn::MakeCall(unsigned char, char, unsigned char, unsigned long, unsigned long, unsigned long) const + 256 20 DBEngine 0x10b438360 Draco::DBPlugIn::SetStatus(Draco::DBPlugIn::State, Draco::DBPlugIn::AddPlugInFlags) + 252 21 FMS 0x10284ab08 FMS::ServerPluginItem::LoadPlugin() + 272 22 FMS 0x10284cc8c FMS::ServerPluginsHelper::UpdatePlugins(unsigned int&) + 144 23 fmsased 0x1000a0258 FMScriptMgr::GetAndUpdatePlugins(bool) + 104 24 fmsased 0x1000a16cc FMScriptMgr::EnablePluginRequest(FMS::EventHelper&, bool) + 240 25 FMS 0x1026fa994 FMS::ComponentBaseThread::Main() + 196 26 fmsased 0x10009fe6c FMScriptMgr::Main() + 336 27 Support 0x10d2ba734 Draco::Thread::RunThread() + 76 28 Support 0x10d2b96a4 Draco::Thread::ThreadUnixProc(void*) + 156 29 libsystem_pthread.dylib 0x197b6ac0c _pthread_start + 136 30 libsystem_pthread.dylib 0x197b65b80 thread_start + 8 The top is higher level, and the bottom is lower level, so work from the bottom up. At line 27, we see it's Draco, which is the name of the FileMaker engine. Line 24 is fmsased running EnablePluginRequest which I presume is FMS trying to load a plugin. Line 21 is LoadPlugin from FMS. Line 18 is the first call to BE itself. 17 is LoadPlugin but inside BE, which is a function in BE. 16 is InitialiseForPlatform which amongst other things does setup for notifications ... which after that you can see OS related functions being called, all around notifications. So this is super helpful, and likely means we need to disable notifications on FMS on Mac - because they shouldn't be active on the server anyway. Thanks, this is a bug, we'll get onto it. Cheers, Nick — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[mw777eds]

Hey @nickorr

The plugin seems to be stable now.
server is a 2024 Mac mini M4 Pro 48gb ram with Sequoia 15.6 FMS 22.01.66

Here is the test file
BaseElements Plugin Tests.fmp12.zip

[jsrcomp]

Thinking there may be something that needs to be updated in the test database, tried running on my laptop the other day, it just gave me the beachball every time I looked at it over the next hour or so. Just tried running in on server (Intel proc on server, Apple on my laptop) and I got the same behavior, been running 11 minutes and I told server to disconnect the 2nd login for PSOS, it’s still running 4 minutes later when I gave it a timeout of 2 minutes for the disconnect

…

On Aug 5, 2025, at 20:47, Nicholas Orr ***@***.***> wrote: nickorr left a comment (GoyaPtyLtd/BaseElements-Plugin#250) There is a test build of 5.1.0 for Mac you can get here : https://www.dropbox.com/scl/fi/gsiybbelyt7lzzdlsztoj/BaseElements.fmplugin.dmg?rlkey=nh3cueigo2wua90eyn8iu17hl&dl=1 I think this solves the notifications issue, but I have at least one other issue with this release : #252 I don't yet know the cause of that one, if it's text or xml related, so there may be other effects. If it loads on your FMS on Mac, then you can run the BE Tests file : https://github.com/GoyaPtyLtd/BaseElements-Plugin/blob/master/Project/Extras/BaseElements%20Plugin%20Tests.fmp12 Hosted on server, it will report all the things that FMS can do and skip any it can't, to confirm any other issues. If there are issues, send me exact details of FMS and OS versions and a copy of the file : ***@***.*** Cheers, Nick — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[jsrcomp]

I concur, the plugin was able to load on server without crashing fmsased

…

On Aug 6, 2025, at 10:36, Michael A Wallace Sr ***@***.***> wrote: mw777eds left a comment (GoyaPtyLtd/BaseElements-Plugin#250) Hey @nickorr The plugin seems to be stable now. server is a 2024 Mac mini M4 Pro 48gb ram with Sequoia 15.6 FMS 22.01.66 Here is the test file BaseElements Plugin Tests.fmp12.zip — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[nickorr]

Thinking there may be something that needs to be updated in the test database, tried running on my laptop the other day, it just gave me the beachball every time I looked at it over the next hour or so. Just tried running in on server (Intel proc on server, Apple on my laptop) and I got the same behavior, been running 11 minutes and I told server to disconnect the 2nd login for PSOS, it’s still running 4 minutes later when I gave it a timeout of 2 minutes for the disconnect
…

Yep, that url is old and not working, and that test should be removed or modified. But also, we should perhaps be putting a timeout on the http calls through all the tests.

I have had on my ideas list to do a new and improved tests file which :

• Has all the tests stored in git, either xml or separate files or some such.
• The FileMaker file is empty and loads everything on startup from the tests location in git, from a chosen branch ( so you can have one file that does test/dev/prod builds).
• Has a way to report back all the info it finds ( including all the version details ) to somewhere here in the repo, so we can investigate.

I have a long todo list ...