#benedict_terminal-ios
idle trenchBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1424818594189021304
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hollow loom
👋 let me have a look, never seen that error before
can you share a bit of code? It seems to be a change to the method definition for the delegate
benedict_terminal-ios
cobalt lance
Someone else got this here before and i've tried everything there and didnt work for me. #dev-help message
hollow loom
ah nice find, I never think to search Discord
cobalt lance
Okay, a bit tricky because my app is in dotnet MAUI and we have a Swift wrapper proxy project that directly integrates the terminal sdk. All works perfectly well in 3.9.1. Will provide relevant code snippets.
hollow loom
yeah I was afraid you'd say that, my guess is that it will be some weird incompatibility with your proxy
Okay I asked my team but no one with experience on this is online right now
cobalt lance
var mobileReaderEventDelegate = new MobileReaderEventHandler(_logger);
mobileReaderEventDelegate.SetListener(this);
mobileReaderEventDelegate.SetReaderName(deviceSerial);
var connectionConfig =
new ProxyBluetoothConnectionConfiguration(locationId, true, mobileReaderEventDelegate, out var err);
_logger.HandleNsError(err);
_stripeProxy.ConnectBluetoothReader(proxyDevice, connectionConfig,
(reader, error) =>
{
if (error != null)
{
_logger.Error("Error occured in connecting to reader. Code: {0} - Description: {1},",
error.Code, error.Description);
return;
}
_connectedDevice = reader;
UpdateDeviceInfo();
_deviceStatus.OnNext(DeviceState.Connected);
});
Since this is quite advanced with your proxy, I think the best approach will be for you to reach out to our support team using https://support.stripe.com/contact and providing all the details (code, exact logs from the reader(s)), etc.
I don't want to ask you even more things here to then have to redirect you anyways