Dimitar Topalov

> @o15a3d4l11s2 By changing build configuration setting dose this work for you? Because I'm also facing same issue `unavailable (14): Transport became inactive on big response`. Please update. By building...

@Lukasa, I never understood why it has to run in build configuration **release** in order to work. Is there some documentation or hint what exactly differs in the grpc-swift logic...

It is much nicer than the workaround I have used 😅 ``` CRUD::field('name')->type('text')->suffix('') ``` and then created a `clipboard.js` file with ``` $(".backpack-copy").on("click", function () { const value = $(this).closest('.input-group').find('input').val();...

I think the problem might be the logic itself. Do you have other possible values for `$entry['numberable_type']` than Place and Employee? Could it be that this is not the correct...

Is there any plan or progress on this?

I tried canceling the move event on certain conditions (like x or y < 0), but then I realised that is not not exactly true, as there could be image...

@tristanhimmelman, do you have plans to resolve these error, or you prefer working on the new version with Alamofire 5?

@RomanPodymov I have used v5.2.1 prior to posting here and I get the same error.

@RomanPodymov , I am using the following: - Cocoapods for installing the libraries - Alamofire v**4.9.1** (I do not want to use Alamofire v5 yet) - AlamofireObjectMapper v**5.2.1** (because of...

This is just a dummy Single View project with the pods pre-installed and Swift version set to 5 in the AlamofireObjectMapper pod. [demo.zip](https://github.com/tristanhimmelman/AlamofireObjectMapper/files/4160199/demo.zip)