MemeGenerator | Generate Image Memes using AngularJS | Computer Vision library

setState accepts a callback as a second param which will be executed right after the state change.

On the other hand, with a dynamic website the server might not send back any HTML at all. Instead, you’ll receive JavaScript code as a response. This will look completely different from what you saw when you inspected the page with your browser’s developer tools.

Src: real python.

In my case also, the website sent back javascript code. The solution is to use requests-html or selenium

Since this isn't about saving the images but just for display purposes, I got it working.

The main problem that you were having is your approach seemed to focus more on the javascript side of things but missed out on the CSS part of it.

There are multiple ways to put images behind text, the most common two are:

1. Setting the images as a background image on the parent element (ie div) then just setting the text within that element
2. Using CSS to absolute position the text on the image and use z-index to layer them

For my answer I chose #2.

Besides misc code clean ups, the main function that I did was:

1. I created a div, and gave it a class of meme
2. I added the image to that div
3. I added the top and bottom text to their own divs and append those to the meme div
4. Using CSS, I positioned the top and bottom text above the image

A few other things, when adding an eventListeners unless it is absolutely needed, I recommend tying them to a specific element and not just the document (or nothing at all which I believe is document anyway). By applying it to the document, any click will be processed, but by tying it to the element, only clicks on that element will be processed.

scr property of your image should be src

For Example: you should have

Remove "()" at the end of

I actually found a solution. Just in case someone has the same problem.

Adjusting the font size for the width works well with my original code:

There's an issue on GitHub regarding this warning:

And here's a comment to why it wasn't dropped yet:

OK so it looks like the new API was only added in Gradle 4.8

I need our Plugin to work for people on 4.4 still, so I think we'll have to ignore this warning for now as people are slowly forced to use a newer Gradle by Play Store requirements.

There's also a second issue where someone posted a fix on his fork. As it was pointed out there, it requires now newer version of Gradle which means it'll break people using the older ones.

In my suggestion, keep your phone connected to your your PC/Laptop while you download and attempt to open it. Use Logcat on android studio, it mostly has all answers or at least errors that lead to the answers. try putting error logs here so we can have a proper look at it.

1) Try the same version of your application that you deployed on Google play store by pushing it through the android studio and see if the problem continues!

2) If same thing happens then put breakpoint on the entry point (onCreate method in most cases in MainActivity class) of your application and Go to Run->Debug "YourProject" option and do step by step debug for each command being executed and see which one is causing problem.

Step #1: Use compress() on Bitmap to save it to a file in getCacheDir()

Step #2: Add FileProvider to your project, configured to serve files from getCacheDir()

Step #3: Use FileProvider.getUriForFile(), instead of your existing code, to get a Uri to put in EXTRA_STREAM

Step #4: Add Intent.FLAG_GRANT_READ_URI_PERMISSION to the Intent before calling startActivity(), so the recipient has rights to access your content