Getting Started

Getting Started Creating your first Fyne app Run Fyne Demo Application and RunLoop Updating Content in your GUI Window Handling Testing Graphical Apps Packaging for Desktop Mobile Packaging Run in a Browser App Metadata Distributing to App Stores Compiling for different platforms

Exploring Fyne

Canvas and CanvasObject Container and Layouts Widget List Layout List Dialog List Theme Icons Adding Shortcuts to an App Using the Preferences API System Tray Menu Data Binding Compile Options

Drawing and Animation

Rectangle Text Line Circle Image Raster Gradient Animation

Containers and Layout

Box Grid Grid Wrap Border Form Center Max AppTabs

Widgets

Label Button Entry Choices Form ProgressBar Toolbar

Collections

List Table Tree

Data Binding

Data Binding Binding Simple Widgets Two-Way Binding Data Conversion List Data

Extending Fyne

Building a Custom Layout Writing a Custom Widget Bundling resources Creating a Custom Theme Extending Widgets Numerical Entry

Architecture

Geometry Scaling Widgets Organisation and Packages

Frequently Asked Questions

Layout and Widget Size Theme and Customisation Troubleshooting

API Documentation

Upgrade to v2.4 Fyne API v2.4 app canvas container data/binding data/validation dialog driver driver/desktop driver/mobile driver/software layout storage storage/repository test theme widget

List My App

Troubleshooting

Some things can not go as expected during setup or in compiling your first app. We try to address these problems here. Remember you can also check your configuration using the Fyne Setup tool.

Compiler Issues

Q: command not found: fyne

A: If you have installed the Fyne command using go install fyne.io/fyne/v2/cmd/fyne@latest but you see an error when trying to run it then the most likely issue is that your Go install has not set up your PATH environment variable correctly.

Go will install tools to the bin directory inside the user’s GOPATH location (normally ~/go) - you can check this by seeing if your PATH variable includes this location. If it seems to be missing then you should update your PATH environment variable to include ~/go/bin, or if you have changed install location then you can use $(go env GOPATH)/bin instead.

Q: build constraints exclude all Go files in …

A: If you are cross compiling you may see an error about go files being excluded, followed by a build failure. When doing a standard Go cross-compile it will automatically turn off CGo. To fix this be sure to set CGO_ENABLED=1 in your compile command.

Q: cc1.exe: sorry, unimplemented: 64-bit mode not compiled in

A: Windows compilation will sometimes complain that 64 bit mode is not available. This is normally because the wrong compiler is installed, or the configuration is incorrect. If you have followed our installation instructions for MSYS2 and MingW64 then make sure you are using the start menu launcher titled “MSYS2 MinGW 64-bit”.

Distribution

Q: Apple macOS says my app is damaged when it is downloaded

A: When files are downloaded on a macOS computer they are marked with a “quarantine” flag so they are checked by the OS for problems. If your application is signed with a certificate purchased from Apple this is not a problem. However if you want to share your software without that cost this error may appear - and on M1/2 computers it is not possible to use the System Settings to allow the app to run.

The fix is to remove the quarantine flag, which you can do by opening the Terminal and executing the following command:

sudo xattr -r -d com.apple.quarantine MyApp.app

Improve this page