# Category: Coding & Scripting

## How to ignore PHP_CodeSniffer warning: Line exceeds 120 characters;

When using codesniffer to check your code, a lot of warnings might appear when the lines are too long:

----------------------------------------------------------------------
FOUND 0 ERRORS AND 4 WARNINGS AFFECTING 4 LINES
----------------------------------------------------------------------
73 | WARNING | Line exceeds 120 characters; contains 162 characters
75 | WARNING | Line exceeds 120 characters; contains 124 characters
102 | WARNING | Line exceeds 120 characters; contains 168 characters
108 | WARNING | Line exceeds 120 characters; contains 121 characters
----------------------------------------------------------------------


To ignore those warnings, we can add // phpcs:ignore as a comment to the end of a (too long) line. For example:

<?php
$message = 'This is my long message. It\'s not only long, it\'s extreeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeemly long'; // phpcs:ignore  ## CocoaPods: pod update/install stuck at “Pre-downloading …” When CocoaPods stops the execution of install or update command, it’s helpful to clean the CocoaPod cache using the following commands: rm -rf "${HOME}/Library/Caches/CocoaPods"
rm -rf "pwd/Pods/"


After this, the update (or install) should run smoothly:

pod update


## Flutter: generating *.g.dart files for json serialization

The full documentation for this is available on flutter.dev

When creating json_serializable classes the first time, you’ll get errors similar to what is shown in the image below.

These errors are entirely normal and are simply because the generated code for the model class does not exist yet. To resolve this, run the code generator that generates the serialization boilerplate.

There are two ways of running the code generator.

### One-time code generation

By running

flutter pub run build_runner build


in the project root, you generate JSON serialization code for your models whenever they are needed. This triggers a one-time build that goes through the source files, picks the relevant ones, and generates the necessary serialization code for them.

While this is convenient, it would be nice if you did not have to run the build manually every time you make changes in your model classes.

### Generating code continuously

watcher makes our source code generation process more convenient. It watches changes in our project files and automatically builds the necessary files when needed. Start the watcher by running

flutter pub run build_runner watch


in the project root.

It is safe to start the watcher once and leave it running in the background.

When Sourcetree keeps asking for password when committing or pushing data to a server, the following solution worked for me:

Go to terminal in your project folder and enter:

git config credential.helper store

git pull


Source (somewhere in between the lines):

## PNG – deactivate interlace to avoid ‘libpng warning: Interlace handling should be turned on when using png_read_image’

I stumbled appon a warning message that was thrown by PHP when handling images with GD lib (e.g. imagecreatefrompng()). The message shown was:

libpng warning: Interlace handling should be turned on when using png_read_image


This message even exists, when deactivating ‘interlace’ with the help of:

imageinterlace($img, false);  The only solution is to deactivate for the processed image(s). This is possible with ImageMagick. To deactivate interlace on all images of a folder, the following command can be used: magick mogrify -interlace none *.png  I used ImageMagick on macos and installed it with with HomeBrew: brew install imagemagick  ## Composer – PHP Fatal error: Allowed memory size of ## bytes exhausted Composer may sometimes fail on some commands with this message: PHP Fatal error: Allowed memory size of ## bytes exhausted <...  In this case, the PHP memory_limit should be increased. Note: Composer internally increases the memory_limit to 1.5G. To get the current memory_limit value, run: php -r "echo ini_get('memory_limit').PHP_EOL;"  Try increasing the limit in your php.ini file (ex. /etc/php5/cli/php.ini for Debian-like systems): ; Use -1 for unlimited or define an explicit value like 2G memory_limit = -1  Composer also respects a memory limit defined by the COMPOSER_MEMORY_LIMIT environment variable: COMPOSER_MEMORY_LIMIT=-1 composer.phar <...>  Or, you can increase the limit with a command-line argument: php -d memory_limit=-1 composer.phar <...>  This issue can also happen on cPanel instances, when the shell fork bomb protection is activated. For more information, see the documentation of the fork bomb feature on the cPanel site. ## Xcode fails to generate source files from intent definition files when using the Legacy Build System The workaround for this problem is the following: First, add a Run Script phase before the Compile Sources phase of your target: xcrun intentbuilderc generate -input${SRCROOT}/PATH/TO/Intents.intentdefinition -output \${SRCROOT}/Intents -classPrefix "" -language Swift -swiftVersion 5.0


Then, add all of the generated files from the output path specified in the command above to all required targets in your project.

As already discussed in Background task in iOS action extension, it sometimes becomes necessary to perform time consuming tasks in the background. This is really important, if such a task would block the user interaction. Especially for action and share extensions, this might lead to some waiting time before a task completes and the extension disappears. After several attempts to realise a working solution, the following code help to extends an App’s background execution time.

This code was described in the article Extending Your App’s Background Execution Time.

## Extending the background execution time in an app

func performTask()
{
// Perform the task on a background queue.
DispatchQueue.global().async {
// Request the task assertion and save the ID.
// End the task if time expires.
}

}
}


## Extending the background execution time in an extension

func performTask()
{
// Perform the task in background.
let processinfo = ProcessInfo()
processinfo.performExpiringActivity(withReason: "Long task") { (expired) in
if (!expired) {
}
else {
}
}
}


As mentioned in the documentation, the ProcessInfo code block is called a second time if the system need to suspend the process:

If your block is still executing and the system need to suspend the process, the system executes your block a second time with the expired parameter set to true. Your block must be prepared to handle this case. When the expired parameter is true, stop any in-progress tasks as quickly as possible.

Important: it’s important that the tasks are executed synchronously. When the end of the block is reached, the thread will terminate and end the execution of your task. If your tasks are asynchron, you can use a loop like shown below to wait inside the background thread until the asynchron task is finished:

// Keep background thread alive until asynchron task ends.
repeat {
sleep(1)